@Andrw0830 For me V2V also shows a blank status for VDDK and I am using version 9.0 of the .tar.gz aswell.
Import of VMs from ESXi works fine and VM get’s shut down on the ESXi side automatically. I do have the little quirks mentioned before though.

@olivierlambert said in XOA 5.110 - Import from VMWare shows "vddk:" without ok or checkmark status:

Is it clear in our doc @Danp to make a snapshot on the VM we want to live migrate, and ourselves? (ie it's not done via the V2V automatically?)

I was also performing tests with the new V2V VDDK feature and noticed that it is required to manually create snapshots on VMWare side.

I was wondering: is there any particular reason that V2V is not creating the snapshots automatically?

I think if it would create the snapshots automatically it would be a great improvement and make the feature more intuitive to use.

Another thing that I noticed:
after successful migration by V2V VDDK tool the resulting VM on XCP-ng side has 2 snapshots:

Are they required? Can they be deleted automatically by V2V feature?

In the old V2V implementation (without VDDK) I did not have these snapshots after successful migration.

Anyways: thank you so much for this great product, I am currently preparing the migration of our internal infrastructure from VMWare to the Vates stack and am feeling great so far about the product and the community!