I have a VM, it's Windows 2000 Advanced Server. I have about 20 of these VM's. This particular one, I installed, reinstalled, uninstalled, and reinstalled the Tools.
No matter what the tools show as "old" or out of date. Even though I know I am updating to the latest version. In fact, on this host I have 2 maybe 3 other W2K Adv Ser VM's (basically same configuration) and those tools work fine.
The Tools out of date is ancillary to the problem, which is that the CPU never drops below 2ghz. That VM isn't doing anything it's idle, and I have this feeling that the tools (not installed or reported as old) have something to do with this odd behavior.
I am about to remove that VM and move it to VM Server, and get it off my ESX host, because it's the only one I have that is causing my grief.
Is there an easy way to fix the tools problem or something to check for?
How many vCPU's are in the VM and how many does ESX think it is supposed to have?
I've seen this before, there's a line you can add to the vmx file which stops this. I'll try and dig up the kb.
Here you go:
http://www.vmware.com/support/kb/enduser/std_adp.php?p_faqid=1217
Message was edited by:
kix1979 shorten link
Try installing the tools from Server 1.0.2.
This fixed the same problem for me with a FreeBSD guest.
Check your VM and make sure that you do not have the wrong Windows HAL. I believe I saw that behavior before when I had a 2000 VM with a multiprocessor HAL and only 1 VCPU assigned to it.
Wes
