Why does a virtualised "Windows XP" running under "Hyper-V Server 2008 R2" use only one of the four allotted virtual processors?

We used the disk2vhd tool to convert a running Windows XP Professional system with a quad-core processor, and attached the resulting image to a guest running under Hyper-V Server 2008 R2.

This VM has 4 virtual processors allotted to it. Everything seems to be normal ("new" hardware required drivers, etc.), but taskmgr shows only one of the allotted 4 uP being used; Device Manager lists all 4 uPs though. Has anybody else encountered this problem before? If so, how can this be resolved (the VM needs 4 uPs for our work).

Is this a potential licensing issue?
ozjonnoAsked:
Who is Participating?
 
kevinhsiehConnect With a Mentor Commented:
Use System Center Virtual Machine Manager if you have it. If not, here's a post that suggests using a 15 day free trial of some Acronis software.

http://williamfaulkner.co.uk/2009/01/easy-physical-to-virtual-p2v-for-hyper-v/
0
 
kevinhsiehCommented:
Install/reinstall the Integration components. It is also possible that you can only use 2 virtual processors, because the desktop OSes only support 2 CPUs. Your XP box was on a single physical CPU that was multicore, but there is no such thing (yet) as a multicore virtual CPU.
0
 
ozjonnoAuthor Commented:
We had doubts about the HAL ourselves and tried installing "integration services," but the HAL upgrade process keeps prompting for a reboot and never gets installed.
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
kevinhsiehCommented:
Can you uninstal the Integration Services and reinstall them?
0
 
ozjonnoAuthor Commented:
Have done that many times before. The following dialog boxes show up after we "insert" the integration services "disk" into the VM:

*HAL Upgrade Required*
"Prior to installing Hyper-V integration services, the HAL in this virtual machine must be upgraded. This will require a reboot of the virtual machine before continuing with the installation process. Are you sure you want to do this?"
[select Yes]

*Hyper-V integration services*
"Upgrading HAL" (activity-bar)

*Restart Required*
"You must restart your system before Hyper-V integration services can be installed. Do you want to restart now?"
[select Yes]

The system then restarts, and after logging in, the "HAL Upgrade Required" dialog shows up again. Seems like it's caught in an endless loop.
0
 
kevinhsiehCommented:
You can try to use the Windows Installer Cleanup Utility to remove the Integration Services from the Windows Installer Database and rerun the installation. I would have a backup of the VM before doing that. Another option is to try to redo the P2V conversion.
0
 
ozjonnoAuthor Commented:
Given that disk2vhd isn't really a P2V tool, could you suggest some other app to achieve that?
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.