Import from VMWare - Error: Can't import delta of a running VM without its parent vdi
-
@jkissane Did the source VM have an existing snapshot when you tried the import?
-
@Danp Nope no snapshots. I've updated xoa to the latest rather than stable version so going to try again with that.
-
@jkissane Please try it with an existing snapshot as I believe that is required.
-
@Danp A snapshot of a powered off VM?
-
@jkissane With ESXi 6.5 & VMFS 5 it should work either way as long as the snapshot exists.
-
@Danp After upgrading to the latest version of xoa (rather than stable) I was able to import both a Linux & Windows VM (both powered down) from ESXi.
The Windows VM gives me a blank screen when powered on under XCP-ng while the Linux VM has dropped to an emergency shell warning that a disk it expects doesn't exit.
Unsure where to go from here if I'm honest.
-
@jkissane Hi !
Did you install xen driver before exporting the VM ?
dracut --add-drivers "xen-blkfront xen-netfront" --force -
That's very likely the issue (for Linux) and for Windows, double check that you are using the right boot mode (UEFI or BIOS)
-
No I hadn't installed any extra drivers but having installed them using the command suggested & re-imported it made no difference as once again I'm back to the same screen as earlier.
This is a Centos 8 VM with a flat disk, no snapshots etc & very low CPU/memory requirements.
-
@olivierlambert For the Windows VM, if I change the boot mode to UEFI then it doesn't boot at all, rather drops me into the UEFI shell. With BIOS I get a brief glimp of the Windows progress bar, the console resizes & then it stays at a black screen with zero CPU usage as far I can see.
-
Just wondering if I'm doing something incorrect here with trying to import VM's from ESX to XCP-ng?
Our ESXi system is running VC 6.7 & ESXi 6.5 on the servers. All the storage for the VM's is external via iSCSI.
We're covered for the VMware setup 'til next Dec so I'm looking at possible alternaitives hence these tests.
-
I don't see any obvious mistake but it's only from a very "far" point of view: it's hard to tell much more without digging a bit more.
My next move would be to boot again the CentOS thing but on a live CD to take a look on the drives from it and see if there's any obvious problem. You can also tinker with the grub menu to double check if you are not using hard coded disks paths and such. If you don't know how to do it, then might worth starting to ask for some professional support (as you can imagine we are kind of busy and despite doing our best with the community assistance, it's hard for us to make very deep investigation in here)
-
@olivierlambert I was able to sort out the issue, it has to do with licensing and the fact that we aren't licensed to with "Live Migration" for this ESXi host.
Essentially this inquiry is solved.
-
O olivierlambert marked this topic as a question on
-
O olivierlambert has marked this topic as solved on
-
Great!
@jkissane please open a new thread if you want to continue discussing your issue
