@MajorP93

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

@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.

Thanks for the information. Do you use ESXi Free or paid license? Just wondering if it's paid then that might be why as I've heard before that ESXi free starting with 6.7, didn't allow warm migration and I remember trying to use Starwind's V2V converter a year ago and it wouldn't work with ESXi 6.7 with the free license installed. That was to import an image into VMWare not to export one so not sure if the license limitation would still effect that.

Ok so wanted to post an update.

With a snapshot created, importing from VMWare will allow the snapshot disks to be imported, but once that's done, the source VM never shuts down and the import process just hangs (have to eventually just stop the task from XOA). Within ESXI, the tasks shows whenever XOA reached out with the last task name of "Nfc Get Vm Files" listed (see image). Is there a reason why creating the VM and inputting the snapshot disks work, but nothing happens afterwards? I've even tried to re-create a Debian version of my XOA just in case maybe building the nbdkit and libnbd manually on my Ubuntu XOA caused the issue, but the Debian version has the same issue including the vddk not showing a green checkmark with an ok status at the top. Someone with a working import, can they confirm if the VDDK is supposed to show an 'ok' status or is it fine with the blank status after the ':'? I've downloaded the "VMware-vix-disklib-9.0.0.0.24742305.x86_64.tar.gz" and dragged it into the XOA window and clicked on the button to import it so that should work.

@Danp Thanks for the suggestion as that was it.

Since warm migration wouldn't work before, I've completely forgot a snapshot was needed before trying the import.

@Danp It's ESXi 6.7.0 Update 3. I do notice a speed improvement when importing the VMs when they are powered off, just the disks won't import when the VM is on.

@Danp

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

@Andrw0830 Run the following command to remove the VDDK directory tree --

rm -rf /usr/local/lib/vddk

It should prompt you to install the library again after doing this.

Thanks for the command. I was able to reinstall vddk, but I still can't perform an import from VMWare. Checking the log, I can see it's reaching out to the esxi host and shows import of disks scsi:0:0 succeeded, but the status of 'importing vms 20', just stays on pending and there's nothing in the Task that's showing it's doing anything. When you check the VM in XOA, there's still no disks at all, so it's creating the container for the VM, but not importing the disks. I do have the free ESXi which I know didn't support warm migration before, so could that be the issue, or does this new method support free ESXi license?

Update: Importing a VM that's powered off still works, so the warm migration is the issue, so whether that's because of Free ESXi, just wanted to let you know.

@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.