Home / server / Questions / 667431
In Process
Scott Szretter
Asked: 2015-02-14 07:54:59 +0800 CST

Why are my VMWare 5 virtual machines not booting when converted over to Microsoft Hyper-V 2012r2?

  • 772

I have a Dell VMWare 5.x environment, but am experimenting with Microsoft Hyper-V (server 2012r2 64). I am using the Microsoft converter utility to move these vm's, which completes fine but the resulting Hyper-V VM does not boot. It shows the Hyper-V logo, then sits at a black screen with a flashing cursor.

On one example Dell machine - an R900 running Hyper-V, I am able to successfully create a NEW vm and install Windows Server 2012r2. It boots up fine, and I am able to connect to it. SO, I believe that would eliminate any hardware limitations, correct?

I have read online, about possibly needing to fix the MBR or possibly hack/replace the HAL. Is this normal, or should there be a cleaner way to convert/move these vm's over to HyperV?

Two examples of VMs I have tried: Windows Server 2008r2 and Server 2012r2 64. I am using MVMC v 3 (latest at the moment off their site)

--

UPDATE:

I tried using a 2008 boot disk (repair function) and it recognizes my OS (though it looks like it's on the 'd' drive). Researching, I found advice to run "bootrec /fixmbr" and some other similar commands and it worked! HOWEVER, I do not like this solution for a production machine. It would be nice to understand and have a solution to covert these without having to 'fixmbr'?

vmware-esxi

1 Answers

  1. EDIT: See this question, which also discusses some of this: Hyper-V VM doesn't boot off SCSI hard drive

    I would check your drive configuration in Hyper-V. Maybe, if there's more than one drive, it's trying to boot to the wrong one. EDIT: No BISO, check the config of the Hyper-V Guest to ensure the proper drive is selected as the boot drive.

    Additionally, if your Hyper-V VMs are version 1, they don't support boot from SCSI, something that ESXi 5.x may have configured for those machines by default. Ensure your boot drive is connected as an IDE drive and see what happens then, or upgrade the VM to guest version 2 if you can.

    Like other commenters, it's hard to say without other info, but (from my experience) these seem to be the most common issues with booting after a cutover. Good luck.

    • 1