XCP-NG VMWare import starts but stays a 0%
-
It's a known issue caused by a recent commit on the Github repo. You can rollback to an earlier commit to get it working, or you can deploy a trial of XOA Premium.
-
Ah, OK.
In the previous tries, I used the CLI to remove the VM so its "ghost" didn't kick around. Is that the best procedure?
K
-
You can delete it from either the CLI or the GUI. Was the VM stopped when you tried the import? This is currently a requirement with ESXi above 6.5.
-
Yes, the VM was stopped.
The weird thing was I could see XO counting the VM (like seeing 1 of 2 on the VM page), but it wasn't something I could see/select and delete; that's why I used the CLI.
K
-
So, I spun up a Premium XOA and imported a Windows 10 VM without any issues.
I then imported a Windows Server 2012R2 (the joys of supporting old software), and it will only show up in the VM list if it's running. When it's off, it disappears. XOA knows there's a VM, as at the top, it says it's showing 3 of 4 VMs.
I also can access the VM's page if I use its UUID in the URL.
So why is the UI dropping the VM? It acts the same way in home built XO as well.
K
-
@kopeck Are you clearing the default filter of
power_state:running, which shows only running VMs? -
@Danp said in XCP-NG VMWare import starts but stays a 0%:
@kopeck Are you clearing the default filter of
power_state:running, which shows only running VMs?We're not going to talk about whether that worked or not.
At any rate, thank you.
I can't seem to get XOA to recognize that Xen tools are installed; I'll keep plugging away on that one.
K
-
What version of the tools are you trying to install? What OS?
-
The XenServer VM Tools. I thought about using the XCP-NG ones for a few minutes, but they looked like they were a work in progress.
Crappy old Windows Server 2012R2, it's to support an older application.
The XenServer VM Tools worked fine on the Windows 10 VM that I imported earlier.
K
-
@kopeck Sometimes it takes a few reboots for everything to settle down.
