Receive updates via email:

 Updates via RSS

Tag Cloud

Blog Archive

Monday, September 22, 2008

Hyper-V and VMWare 2.0 - Make them Work Together

A little over a week ago, I wrote that I could not get Microsoft Windows Server 2008's Hyper-V and VMware 2.0 RC2 to run together on the same machine.

A couple of days after the post, Steve Graegert mentioned that he had a work around (although klunky) that he posted on his blog.

In his post, he mentions a boot loader option to bypass the Hypervisor loader at boot time for Windows 2008. You still cannot get both Hyper-V and VMWare 2.0 to run at the same time.

Still it gives you some options, to at least run both -- albeit you have to reboot. Here is his process and the outcomes I experienced:

1. Go to a command prompt.

2. Enter the command: bcdedit /copy {default} /d "Boot without Hypervisor"

3. The GUID of the boot is returned in the confirmation of "The entry was successfully copied to {GUID}. Extract that GUID, including the braces.
4. Now execute the command after replacing the "GUID" with the information that you copied from the above set: bcdedit /set {GUID} hypervisorlaunchtype off

Here is the result:
Installing both Hyper-V and VMWare 2.0 in Windows 2008

6. Next, I would recommend taking a quick browse to Start --> Control Panel --> System --> Advanced system settings --> Startup and Recovery --> Settings. Change the "Time to display list of operating systems" from 30 seconds to your desired values. Otherwise, the system will pause for 30 seconds if you do not provide input on every subsequent reboot. Alternatively, if you are as annoyed with Hyper-V as I am right now -- you may choose the default operating system as "Boot without Hypervisor".

Startup and Recovery Settings from running Hyper-V and VMWare 2.0 Server

As far as the outcome, this worked perfectly for me -- I was able to reboot and enter into Windows 2008 without Hypervisor -- the underlying support for Hyper-V - loading up. This enabled me to install and run VMWare 2.0 Server without having to remove the Hyper-V role. Thanks Steve!

Interestingly, even without loading Hypervisor -- the three Windows 2008 services (Hyper-V Image Management Service, Hyper-V Networking Management Service, and Hyper-V Virtual Machine Management) still start up. Would Hyper-V still possibly start?

Nope, not a chance. You can get to the Hyper-V Manager console, but when trying to start a Virtual machine, you are greeted with the following message:

An error occurred while attempting to change the state of Virutal Machine XXX.

The virtual machine could not be started because the hypervisor is not running.

The virtual machine could not be started because the hypervisor is not running. The following actions may help you resolve the porblem:

1) Verify that the processor of the physical computer has a supported version of hardware-assisted virtualization.

2) Verify that the hardware-assisted virtualization and hardware-assisted data execution protection are enabled in the BIOS of the physical computer. (If you edit the BIOS to enable either setting, you must turn off the power to the physical computer and then turn it back on. Resetting the physical computer is not sufficient.)

3) If you have made changes to the BOot Configuration Data store, review these changes to ensure that the hypervisor is configured to launch automatically.
Still, it was worth a try!