XCP-ng is back to FOSDEM again for the 10th time, come to visit the Xen/XCP-ng stands !
https://fosdem.org/2026/stands/
Check upcoming Vates announcement at:
https://vates.tech/blog/?q=fosdem
If any interest we can setup a community gathering.
ps: Post to be updated before the event for up to date info
@nikade can you try a journalctl | grep 'nbdkit logs' ?
new branch with more fixes ( feat_exposes_esxi_export ) the main fix is a >= that should have been a > https://github.com/vatesfr/xen-orchestra/pull/9411/changes#diff-f0de876ee608dac8d272996fbb8fa63ec76473bd260ad5abf1995a805866d1beR130 hopefully I am not paid by the character. Don't forget to do a yarn build at the root of your XO and restart it.
this also expose a way to export a disk from an esxi/vsphere with xo-cli.
First install xo-cli with npm install -g xo-cli and register it https://docs.xen-orchestra.com/architecture#xo-cli-cli
xo-cli.mjs esxi.exportDisk host=ipOfEsxiOrVsphere user=EsxiLogin password='PlzDontEnter!' vm=3 disk='scsi0:0' @=/mnt/ssd/export/out.qcow2 format=qcow2
You can check that the export is valid with qemu-img check /mnt/ssd/export/out.qcow2
fbeauchamp opened this pull request in vatesfr/xen-orchestra
draft
feat(xo-server): expose an api method to export a disk from vmware
#9411
I recreate my ZFS pool.
But next time or for other stuck with this kind of issue, I think you should start to rename your ZFS POOL.
I think the old ZPOOL name stay in XO configuration shadow settings.
To rename a ZFS pool, export it with
zpool export [poolname]
and then import it with the new name using
zpool import [poolname] [newpoolname]
And then recreate (sr-create) your STORAGE in XO
