Hyper-v and Virtual PC 2007: Some Cohabitation Issues

I recently started to work with Hyper-v to build a 64 bit environment as Virtual PC 2007 is not supporting it.

I started to go back and forth between Hyper-v and Virtual PC 2007. I immediately noticed that my all my vms in Virtual PC 2007 would not perform well. They would take forever to start, the Active Directory indices would systematically be rebuilt on start, some services could not be started properly, and the overall performance was very poor.

The problem is coming from the fact that Hyper-v is binding itself to the hypervisor process not allowing any other applications to use that process. As a result, those other applications, such as Virtual PC 2007, get a filtered access to the CPU instead of a direct access.

Steps to follow to avoid issues

Set the following three services to be started manually:

The IT Leader's Guide to Multicloud Readiness

This guide provides practical key insights and important factors to consider to make informed decisions in your multicloud journey.

Download the Guide

Before you use Virtual PC 2007, open a command prompt window and enter the following command:

sc config hvboot start= disabled

After entering the command, reboot your machine.

Before you use Hyper-v, open a command prompt window and enter the following commands:

sc config hvboot start= auto

net start hvboot

Now you can start Hyper-v manager and start the service manually: