Why won't a Hyper-V VM boot after being converted from VMWare ESXi?
Solution 1
Instead of converting the disk, if you have access to System Center Virtual Machine Manager, you could to a Virtual-to-virtual (V2V) conversion of the server.
Solution 2
If you still have access to the original VMware virtual disk you could convert it using http://www.starwindsoftware.com/converter I do this often and it works a tret.
David Mackey
Love to code: Python, JS, C#, PHP, SQL, VB.NET, HTML, CSS. In ancient days I coded in QuickBasic, ASP, and VBScript. I'm a friendly introvert with solid communication skills. I work hard and have refined problem solving skills. When I was younger I worked in a variety of industries (commercial fisherman, stone mason, lawn care, factory, custodial, youth leader). I settled on IT and have experience working in a startup, higher education, and with non-profits.
Updated on September 18, 2022Comments
-
David Mackey over 1 year
I was using 5nine's converter to move over a VM from VMWare ESXi 4.x to Hyper-V. However, 5nine failed to create the new machine, although it did successfully move all the drives over...so I tried creating a new machine using the moved disks. When I boot it up it says, "Boot failure." Any ideas why? I'm guessing that something needs to be done so that the Hyper-V machine can read the file correctly to boot off of it?
-
Falcon Momot over 11 yearsIt is good to know specifically how you converted it, and what operating system the VM runs. You may also have accidentally switched from BIOS to EFI or the other way around, but it's impossible to say with only this information.
-
David Mackey over 11 yearsIt is running Windows Server 2008 R2. I believe the issue is that the drive on VMWare was SCSI and on Hyper-V it needs to be IDE to boot off of. Any ideas on how to make it so that the drive will be IDE?
-
HopelessN00b over 11 yearsWhat? Why does it need an IDE drive to boot? You convert it to a Windows 2000 VM or something?
-
Chris McKeown over 11 yearsErm, chaps, perhaps it has something to do with the fact David is absolutely correct, and that Hyper-V machines can only boot from VHDs or pass-through disks attached to the virtual IDE interface. From a performance perspective, it makes no difference though.
-