I'm migrating from VMWare Workstation to Hyper-V. I have a specific VM that it has a single VMDK file with 2 distinct drives inside it, and I've been unable to get it to boot. I converted the VMDK file to VHD using WinImage, and then I used Hyper-V to convert from VHD to VHDX. I can tell it worked because I can mount the VHDX file, and it will successfully mount 2 distinct drives in my Windows 10 Professional, and all the data is there. When I boot up the VM in Hyper-V, I'm getting the
Start PKE over IPv4 message.
After, I get this screen
I checked in PowerShell, and the boot sequence is correct
$boot = Get-VMFirmware -VMName "TravelCash Delphi 7" $boot.BootOrder VMName BootType Device ------ -------- ------ VM10 Drive HardDiskDrive (Name = 'Hard Drive on SCSI controller number 0 at location 0', VMName = ... VM10 Network VMNetworkAdapter (Name = 'Network Adapter', VMName = 'TravelCash Delphi 7') [VMId = 'de...
Below are the mounts that I get then I mount the VHDX file: As you can see, 2 drives are mounted into Windows 10 when I ask to mount a single VMDX file, and Hyper-V is probably getting lost, and it's not finding the right partition to boot. Is there any way around this? Splitting the VHDX file into 2, one for each drive? Or maybe converting the mounted file into separeate VHDX files? Or simply telling Hyper-V to boot correctly? Thank you.
I added a SCSI DVD with a Windows 10 ISO, and it displayed the message that it was booting from the ISO, and then it failed as well