0

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. Start PKE over IPv4 After, I get this screen Boot 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: Mounts 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.

EDIT

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

Booting with DVD

Improve this question
13
  • What happens if you set a Windows boot ISO as the CD/DVD?
    – harrymc
    Commented Mar 10, 2019 at 16:22
  • What exactly do you mean? Boot with a "freash" Windows ISO on the CDRom, and re-install the OS?
    – Pascal
    Commented Mar 10, 2019 at 16:44
  • See if the boot starts at all from the ISO. If it does, try to do Startup Repair. What is the Windows version of the VM?
    – harrymc
    Commented Mar 10, 2019 at 16:49
  • Windows 7. I'll try to boot it with a Windows 10 media.. that's the only one I have
    – Pascal
    Commented Mar 10, 2019 at 16:51
  • You may use it as test to see if the VM boots at all. But for startup repair you need to download a Windows 7 ISO from here. Note: To address me, add @harrymc to the comment so I'll be notified of your comment.
    – harrymc
    Commented Mar 10, 2019 at 16:54

1 Answer 1

Reset to default
1

Windows 7 is not supported in Generation 2 VMs. Generation 2 VMs must also be 64bit.

Beyond that, realize, that you've changed the entire underlying hardware here, converting the disk type doesn't make up for the massive virtual hardware change (motherboard, disk controllers, etc). Also, its important to remove the VMware Tools before doing any conversion.
You will need to use a Generation 1 VM if you want to use Windows 7 with Hyper-V.

See: https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/plan/should-i-create-a-generation-1-or-2-virtual-machine-in-hyper-v

Improve this answer
2
  • I was using Generation 2 VM. That is certainly one of the main issues.
    – Pascal
    Commented Mar 12, 2019 at 18:04
  • I recreated with a Generation 1 VM, and it booted correctly. I was able to uninstall VMWare Tools later without a problem
    – Pascal
    Commented Mar 17, 2019 at 4:09

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .