Wednesday, September 28, 2016

Booting Hyper-V created virtual machines with VirtualBox

At work the other day I was trying to run the Microsoft provided Hyper-V virtual machine (VM) demonstration setup for Team Foundation Server 2010 and Project Server 2010 integration and kept getting blue screens over and over again during boot when using the .vhd file as the existing disc in a VirtualBox VM.

I let it keep rebooting but couldn't get the screen to stay up long enough (or get a screen shot quick enough) to determine what the error code was. I figured it had to be a "hardware" related issue between the two VM hosts and played around with the machine settings until I got it to work.

It turns out that the .vhd files created in Hyper-V are created as IDE drives. Using these images in Hyper-V would not cause a problem as that is what it expects. VirtualBox, on the other hand, defaults new machines to use a SATA controller; which was the cause for my blue screen loop. Simply changing the machine settings to use an IDE controller instead allowed me to boot up the machine and now I am able to use the integration demonstration VM.