OVA import does not import VHD
-
I am migrating from XenServer to XCP-NG and export my VMs as OVA files. On the import however, it shows there is no attached disk so, for example, I am importing a VM with a 200Gb disk, and the OVA takes hours to import and shows 200Gb but the disk does not so I end up with an empty VM and have to then extract the OVA and import the VHD file separately.
This does not seem like correct behaviour as it would therefore seem to defeat the point of the OVA file being everything included? Is this a setting when I export from XenServer perhaps, even though it appears to create the OVA just fine and I can import the files - but have to one at a time.
-
What process are you using to perform the import?
Are you aware that you can perform an in-place upgrade from xenserver to xcp-ng?
-
- Inline upgrade is better, if you can't, migrate VMs from XS to XCP-ng, no need for conversion
- In the case you want to export your VMs for some reasons, use the default XVA format which is entirely supported both ends.
-
@danp I know I can do an inplace upgrade but this is also replacing the entire system (host and storage) which are old so it made more sense to set up the new system and then migrate over to it.
-
@capeschools In that case, @olivierlambert's advice is best --
migrate VMs from XS to XCP-ng, no need for conversion
-
@danp The problem I am having is with the XVA - works perfectly with anything Linux....with any Windows server I try the VM starts up and then within 5-10 seconds fails and shuts down.
So an XVA export from XenServer takes 1/4 the time of the OVA export but does not start up on XCP.........
-
@capeschools if you have the 2 pools up at the same time, you can just connect the 2 pools to XOA and then do a live migration, that's the way I usually do it.
-
Double check you have virt extensions enabled on the new host.
-
@olivierlambert how exactly? When I search for XOA extensions I find a single article related to whether XOA can run on a host or not. Obviously in my case the host is running XCP perfectly fine but there are issue with VM imports?
-
@capeschools I think he means in the BIOS
-
You issue might not be related to VM import, but related to the fact your hardware doesn't have virt extensions enabled in your BIOS. That would explain why your VMs are shutting down after few seconds.
-
@olivierlambert But it is not all of them - surely if that was a factor they would all exhibit that behaviour? I currently have a 2012 and 2019 server imported without issues (apart from the original issue of the XVA import not seeming to work) but an OVA and then VHD import worked. I also have half a dozen totally different linux systems running without issue so it is not everything at all.
-
Maybe those Linux are PV guests?
-
@olivierlambert Actually everything is HVM so my guess is the server is configured just fine but I'll shut it down tomorrow and double check the bios anyway just to make sure.
I'll keep plugging away but its a pain when it takes over 24 hours to export the VM - not sure why but I've had mixed success using a backup/restore process but I'll keep going.
Thanks for everyone's thoughts on this.
-
@capeschools Just as an FYI to complete the thread - VT is enabled by default on the HPE server.
