Solved - Migrating from Hyper-V to XCP-NG and guests not booting their VHDs
-
Hi all,
Looking into migrating from Hyper-V to XCP-NG and followed the official migration guide. I have a healthy mix between Microsoft and Linux guests. And starting with my low priority Linux guests as a test-move.
So what I did for my current (Linux) guests of my Hyper-V server is (HP DL380 Gen9):
- Stopped the guest
- Exported the VM to my Windows host
- Converted the VHDX to VHD
Then on my XCP-NG Host (HP DL380 Gen9) that is using thin-provisioning (EXT):
- Imported the VHD
- Created the new guest in XCP-NG using the correct template and attached no (new) disk
- Waited for the upload to complete
- Attached the uploaded VHD to the correct guest
- Booted
- Stuck on boot (no progress in either BIOS or UEFI mode)
The conversion methods I've used were the build-in converter of Hyper-V (VHDX -> VHD with dynamic option set, existing VHDXs are already dynamic to save on storage cost/size).
When I've noticed that didn't worked, tried the Solarwinds converter as suggested on many topics. Unfortunately the same result.
Probably doing something wrong, but the logs don't seem to output any error at all.Anyone any ideas? Probably I'm missing something
Thanks!
PS: I have 1 guest working without any issues by doing the same steps as I've described. The other 2 guests will simply not boot.
-
@rtjdamen Bingo!
A friend of mine suggested the same, tried to first do an online repair on my Hyper-V host.
When that failed, I finally tried it in XCP-NG and loaded the Windows disk, started the repair and that solved it! -
@DonZalmrol what is the exact issue u run into? Are u running into an import error or do you see issues with booting the guest?
-
Also, do you identify any difference between the working imported guest and the "broken" ones?
-
Seems it was an issue with one guest, the others imported and ran fine. Very odd issue! Might be a Windows issue as I'm experiencing the same in Proxmox as I'm currently testing out both hypervisors atm.
Besides some spec differences, not much between the machines, it's a mix of Windows and Linux machines.
In Proxmox however I'm getting a bit more output followed by BSODs that mention "system thread exception not handled" and "page fault in nonpaged area" when trying to "repair" the OS by injecting the VirtIO drivers, upon loading startup repair it simply BSODs.
-
@DonZalmrol maybe you have an corruption inside the disk?
-
@DonZalmrol i was just thinking, could it be there is anything left from vm tools or drivers? I know we had this kind of issues when vmware tools were installed (they should not be if u use hyperv), maybe something to check.
-
@rtjdamen Bingo!
A friend of mine suggested the same, tried to first do an online repair on my Hyper-V host.
When that failed, I finally tried it in XCP-NG and loaded the Windows disk, started the repair and that solved it! -
@DonZalmrol good to hear! Another good migration solved!
-
O olivierlambert marked this topic as a question on
-
O olivierlambert has marked this topic as solved on