Import from VMware - Uploaded VDDK, now stuck on 'checking'

[JCS-RVK]

I have a new xcp-ng pool with two hosts using XO from sources . I went to import a VM from VMware and was prompted to upload a Broadcom VDDK archive. After uploading, the Import from VMware page just shows 'checking'. Past pools I've set up did not prompt for the VDDK, which makes this scenario seem odd to me. Any idea why this is happening and what I can do about it?

[DustinB]

@JCS-RVK You likely need to install the dependencies to use with VDDK.

This is a WIP from the vates team where you can find information regarding it here https://github.com/vatesfr/xen-orchestra/pull/8840

My guess, and I'm still sorting it out for my GH is that you likely need to run sudo apt install libnbd-bin nbdkit nbdkit-plugin-vddk on your XOCE installation, but that is just a guess at this time as the VDDK version number is also in flux (going from 9 to version 8 ) etc.

fbeauchamp opened this pull request in vatesfr/xen-orchestra

closed feat(V2V): use vddk and disk generator for import #8840

[john.c]

@JCS-RVK said in Import from VMware - Uploaded VDDK, now stuck on 'checking':

I have a new xcp-ng pool with two hosts using XO from sources . I went to import a VM from VMware and was prompted to upload a Broadcom VDDK archive. After uploading, the Import from VMware page just shows 'checking'. Past pools I've set up did not prompt for the VDDK, which makes this scenario seem odd to me. Any idea why this is happening and what I can do about it?

The VDDK prompt when going VMware to Vates migration, is something new. This when perfected will enable more reliable migrations, as the vSphere API method is very flaky indeed. Especially when considering, issues involving Broadcom’s and previously VMware’s alterations to that API.