VMware import stuck at "Importing..."
-
XO or XOA? If XO from the sources, the commit number should be the same on
masteras we speak now. Otherwise, upgrade. Also, check your Node version
-
@olivierlambert
XO from the source. I'm at c8bfd (22.09.2023).
But apparently there are newer commits.
I'll upgrade. -
Okay, and what about Node version? Even if I suspect the issue is more on the ESXi side… But I'm far from being an expert in there to check what's going on…
-
Node: v18.17.1
-
That looks fine to me
-
okay.
I'm also think (as I write this) that something might be wrong with the ESXi setup. So, I should check the ESXi logs.
It's interesting though that other VMs migrated just well.On the XO/XCP-NG side, are there any other log files I can look at besides the one for the import job?
-
You can check the
xo-server's direct output.But yeah, I think ESXi is a better lead. Maybe for many disks at once or bigger disks it explodes. I have to tell I discovered with very much surprise that ESXi wasn't really resilient when exporting disks
-
ok.
maybe I find a clue on the ESXi logs. And when not. I'll take my chances using clonezilla. -
@s-master I was exporting some VMS from esxi via XO a few months ago and exporting machines with one or two drives seems to work okay. Failing that, can your esxi system export to OVA?if not, that, your clonezilla approach will probably work. Sometimes you just have to bite the bullet and start over again from scratch. It sucks, it's horrible but it is better than a half-assed copy that flakes out at you at random times.
-
Hmmmmm I need to look back through some of my old posts and notes but I had a similar issue with a VM with large number of disks. The disks themselves being big wasn't the issue, it was just having a huge number of them that eventually cased a problem. Ended up migrating by moving a single VHD and rebuilding things (the specific system didn't really "need" all the VHDs so it was an easy fix for me, wouldn't be the case here haha).
If you are trying to reduce the number of hosts though, why would migrating the VCSA help? If you're powering off a host then wouldn't you not need the VCSA to be running anyway? Or do you have more than 1 ESXi instance? Might be easiest to just migrate it to another ESXi host if that's the goal, since you won't need the VCSA once you fully move to XCP-ng (assuming you are doing so).
