VMWare to Hyper-V

bmagnant · Thu Jan 13, 2022 8:29 pm

Good afternoon,

I just ran a migration from VMWare to Hyper-V. All of the disk were created just fine, but the VM was a mess. It looked like Gen2 with a collection of IDE and SCSI disks. I deleted the VM and then manually made a new one and attached the disks. When I booted it, I just got the flashing cursor prompt. So I shut it down and ran my favorite boot repair tool and all was well. I think the vmware VM was a P2V at some point in the past, so it may have already been a mess.

Did I do something wrong? There aren't a lot of choices when you do the migration.
All's well that ends well, just curious if I could save myself some steps in the future.

Thanks,
Brent

Fri Jan 14, 2022 12:53 pm

StarWind V2V Converter converts one VM format into another or does P2V conversion. The problem you faced looks to be related to drivers and the way a hypervisor operates with the VM.
Locking to the specific Generation is done now based on the machine boot option. It is done automatically now but we are working on making it flexible. Stay tuned.