Quote:
Originally Posted by taylorkh
I noticed a couple of times recently when running the XP VM that System Monitor showed one CPUs maxed at 100%. It turns out that vmwareplayer-deamon was the offending process. I can kill the process with no ill effects and it comes back at 0% CPU.
|
Troubleshooting virtualization performance is always interesting because there's many things to consider like the guest itself (say the actual necessity to run 2 vCPU's, running UP or MP HAL, running VMware tools or not, guest configuration) the virtualization product (it's version and type as in Player vs Server leaving out Workstation and ESXi, configuration) and virtualization host specs and performance (partitions on separate disks and controllers, scheduler, IRQ balancing etc, etc) but in general you can say using virtualization doesn't mean any utilization or boundedness will automagically disappear (doh).
If you however mean only one single core is kept maxed out constantly and for prolonged periods of time then it would be interesting to see what keeps it maxed out by checking host and guest logs (which ones I don't know: I run VMware server (v1) but at times CPU utilization will max out for me as well) or running 'strace' on the offending process. OTOH this may be a
recurring issue so one other avenue could be to test out another product altogether like VirtualBox. You may find (or not) VB uses up less CPU time.
