Virtual processors are medley dynamic pieces of pie that the host server splits off. I would recommend changing the number of processors to 4 on the xp machine and see what happends
Main Topics
Browse All TopicsDear EE experts,
I have a Hyper-V Server 2008 R2 with a single guest VM running Windows XP SP3 and a custom thin client's terminal server software. My problem is that this hyper-V server has four processors and five Gb of RAM. In spite the fact that the server itself is a "strong" computer, the Windows XP machine shows me that the proccessor usage is nearly always over 50%. Ok, this is by csrss.exe, I love it for this sometimes. But when I look at the Hyper-V server over a terminal service window AT THE SAME TIME, it shows me that the Hyper-V Server 2008 R2's proccessor usage is 0-4% !!! Why? I think it should show me nearly the same thing that XP shows. What did I misconfigure?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
CPU performance shown by the server and within the vm will always be different. Some technical detail about how the vm interacts with the system will always yield different numbers when watching stats like cpu usage, disk queue length, etc. A Microsoft MVP on their newsgroups said the numbers from within the guest OS are what you should trust, not the server.
Is the XP vm actually performing badly? Or are you just worried because the cpu is at 50%? Increasing the number of cores the vm has access to would be the simplest fix, but there's one unwritten caveat that can negate this option. When you install the guest OS on a vm, if you only have one CPU assigned to it, the installed OS will only ever use one CPU. When I setup my vm's, I always assign them 4 CPUs before the install, then scale it back afterwards. This tidbit came straight from the mouth of a Microsoft regional rep helping me setup my first 2008 Hyper-V install.
To elaborate on what I stated before, if your XP VM was setup for 1cpu, then the hardware abstract layer is using ACPI Uniprocessor kernel instead of the ACPI Multiprocessor kernel. Forcing more than one cpu on the system could have very negative effects, like those you were seeing. You might be able to do an inplace XP reinstall (boot off an XP disc, do not choose Repair the first time you see it, but a few steps later, choose repair when you see it again) if you want to get it updated to use the multiprocessor kernel, but as I've never tried, I'm not sure if that would work.
Business Accounts
Answer for Membership
by: MCSA2003Posted on 2009-10-01 at 04:28:15ID: 25467539
When you installed Windows XP as a virtual machine, Hyper-V dedicates a certain amount of the processor to support the OS. The reason you are seeing a low usage in the Server is because you are seeing the entire processor usage for the entire server. The reason your seeing a lot of usage in the XP partition is because your seeing just the XP processor power which is only a small portion of the entire server processor. It is hard to explain in text, so here is a link that may help you understand a bit more.
ual_pc_guy /archive/2 008/02/28/ hyper-v-vi rtual-mach ine-cpu-us age-and-ta sk-manager .aspx
http://blogs.msdn.com/virt