@Danp When I go through the Import steps and hit the Import button on the bottom, I see it spinning and in the past, you'll see the process added to the Tasks list, but nothing new gets added to the Task list. When you go to VMs, it does show the VM powered off, but no disks listed.

Do you have a manual way of applying the VDDK to XOA or a script file I can run via cli on the XOA server so I know the VDDK is truly applied.

To give a more overview on what happened, when I had the VDDK wizard come up to choose the tar file to install, the libnbd plugin I had wasn't installed properly, so I wonder if that's why the VDDK didn't get installed properly. Now that I have both plugins installed, I need to repeat the VDDK install.

Hello XOA community,

I'm contacting you as when trying to import the VDDK file that I've downloaded from Broadcom's site so it could install for XOA, the spinning circle for the import wizard just kept spinning and never completed. After 15+ minutes, I've restarted XOA services and now when you go into Import > From VMWare, I get that all the other components are good, but the VDDK shows 'vddk:' with no green checkmark or ok listed.

Is there a way to get back to the import VDDK screen or install it manually for my XOA? I'm using XOA built from the latest sources.

@rtjdamen As of writing this, I don't see any VMs VDI's listed as being attached to Control Domain. I have 10+ VMs on 3 XCP-NG 8.3 servers in one pool so I'll let you know if we come across that.

@flakpyro I usually don't keep snapshots on my VMs and just have it create snapshots as part of the NBD/CBT backups and have it purge then afterwards. I've tested created a standard snapshot (without memory), deleted it and did a backup and it was able to use the old NBD and CBT chain without error.

@rtjdamen I just have the migration network issue so thought you were referring to that so not sure about the control domain part. Is there a way to check or know if we are affected?

@rtjdamen I can confirm in our environment with XCP-NG 8.3 and XO from sources (from January's end of month release) that we have this exact issue. To confirm what happens is if you define a default migration network during a VM migration, CBT gets disabled and the next backup displays the unable to do CBT on this VDI error. This happens on shared NFS SR on same pool.