Hi,
We are currently working on a tool to better industrialize VM import from VMware into the VMS stack, based on N8N (https://n8n.io). Stay tuned !!!

Hi @nasheayahu,

1/ are you running the latest XO from source ?
2/ did you follow this to create the ZFS volume => https://docs.xcp-ng.org/storage/#zfs ?
3/ did you try with "ext" type instead ? or your requirement is QCOW2 with ZFS ?

The "import QCOW2" is currently not yet implemented, hence the API error (it should have been not permitted actually); it should be merged in the next XO release.

Hi @mdm,

Here is the response from a SME
1-

• XO get the VM metadata through soap api and create the vm /network
• XO use the nbdkit + nbdkit-vddk package , connecting to each disk
• XO connect through NBD to nbdkit
• XO list the allocated blocks
• XO create the disk
• XO read the block and import the data into the disk (though a vhd or qcow2 stream depending on the size)

2- though XO. There is a lot of disk transform occuring here

3- not anymore, it was too brittle, especially on when the disk are locked or not. Also it was not scaling too well
4- see 3- +
vddk transfer is overwhelmly faster that previous access through http, is compatible with VSAN and don't lock the disks.

(+ also see https://xen-orchestra.com/blog/xen-orchestra-5-110/ section "VMware to Vates (V2V)" where we made key improvements)

@abudef we'll add it in the near-term (June hopefully) as QCOW2 support is a major update in the VMS stack !

@jr-m4 Thank you for this feedback. We'll try to make it better based on this !

@nasheayahu so you're actually trying to import those QCOW2 VDIs, not creating them, right ?
You'll have to wait for the import feature for QCOW2 which is coming soon.
You should be able to create a brand new SR with QCOW2, but be aware of the known issue on ZFS with large VDIs (see https://xcp-ng.org/blog/2026/05/05/qcow2-is-now-ga-in-xcp-ng/).
Did you install ZFS on your host ? see https://xcp-ng.org/blog/2018/08/03/xcp-ng-with-zfs/

Hi @mdm,

Here is the response from a SME
1-

• XO get the VM metadata through soap api and create the vm /network
• XO use the nbdkit + nbdkit-vddk package , connecting to each disk
• XO connect through NBD to nbdkit
• XO list the allocated blocks
• XO create the disk
• XO read the block and import the data into the disk (though a vhd or qcow2 stream depending on the size)

2- though XO. There is a lot of disk transform occuring here

3- not anymore, it was too brittle, especially on when the disk are locked or not. Also it was not scaling too well
4- see 3- +
vddk transfer is overwhelmly faster that previous access through http, is compatible with VSAN and don't lock the disks.

(+ also see https://xen-orchestra.com/blog/xen-orchestra-5-110/ section "VMware to Vates (V2V)" where we made key improvements)

Hi @nasheayahu,

1/ are you running the latest XO from source ?
2/ did you follow this to create the ZFS volume => https://docs.xcp-ng.org/storage/#zfs ?
3/ did you try with "ext" type instead ? or your requirement is QCOW2 with ZFS ?

The "import QCOW2" is currently not yet implemented, hence the API error (it should have been not permitted actually); it should be merged in the next XO release.

Hi,
We are currently working on a tool to better industrialize VM import from VMware into the VMS stack, based on N8N (https://n8n.io). Stay tuned !!!

@jr-m4 Thank you for this feedback. We'll try to make it better based on this !

@colomb said:

I really miss the description column XO5 has in the default/home view. I understand space is limited for the tree view, but maybe it could appear when a host is selected in the tree view?

In XO6, you will see it if you click on the eye at the end of the row, then on the right panel.
Is this OK ?

@robbie-c Very clear, thanks. We will change this !

Hi @robbie-c, could you send a screenshot ? is that in XO ?

@acebmxer https://xcp-ng.org/forum/post/103160
no, that was about this:
"When creating vm in v6 and renaming the disk name. You can only enter 1 letter at a time. You have to keep clicking then typing the next letter. No other field has this issue."

@acebmxer this should be fixed in the latest 6.4 release. Can you please confirm ?