the new code is now in master
XO Team
Developers of Xen Orchestra
Posts
-
RE: Need FeedBack: New version of the File level restore
-
RE: XO Backup Error: VDI_IN_USE(OpaqueRef:.., destroy)
@itservices Hi,
We did not forget you, working on it! -
RE: How to Setup IPMI in XO
@MajorP93 Nice job, i'm thinking about working on an api route to have those infos without needing to go to the server console
-
RE: XO Backup Error: VDI_IN_USE(OpaqueRef:.., destroy)
@itservices It may be a storage or a xo issue. You can try to restart xo-server and retry the backup. If it is solved, it was an issue with xo-server not freeing your vdi. If it still happens, it will be a storage issue
-
RE: REST API create_vm returns task URL that doesn't exist?
Hi @DevFlint,
tasks are now correctly visible in the swagger documentation -
RE: How to revert VM to snapshot
Hi @slavavrn,
FYI, its now possible to revert a snapshot via the REST API.
POST /vms/:id/actions/revert_snapshot
And the body of the endpoint:{ "snapshotId": <snapshot-id> "snapshotBefore": boolean (optional) } -
RE: XO Backup Error: VDI_IN_USE(OpaqueRef:.., destroy)
@itservices Hi,
It seems the parent of the backup chain is not found (a delta backup links to another delta and another, until you have a full backup, it seems a backup on this chain is missing).
Can you restart a backup chain to have a full backup? You can do it by reducing the retention in your backup job. -
RE: How to Setup IPMI in XO
@Andrew Hi, i'm the one that made the plugin, the documentation is in progress. Meanwhile, can you post the result of running
ipmitool sdr list? You might find some leads as to which regexes should work for your particular host.
Also you can checkipmitool lan print(be carefull not to share ip's or sensitive info ). -
RE: 🛰️ XO 6: dedicated thread for all your feedback!


Here is a small usability suggestion. In the Resources dashboard, in Pool view and Host view, positions of CPU and RAM are swapped. I occasionally get a brain freeze when switching between Host and Pool dashboard.
Right, thanks! We'll change this !