The host does not use cpuspeed or any other cpu throttling.
In fact, the processor isn't even capable of it.
I turned off Time Sync, since that only keeps the client from losing
ticks (and made the problem worse). Here the problem is that it seems
to be inventing extra ones. I'm now using ntp to keep the client in
sync with a local ntp server, but that seems lame.
All the other posts I've seen close to this topic appear to deal only
with problems with x86_64 processors. My processor is a 32-bit Xeon.
Does anyone have any ideas?
--
Alexander N. Spitzer
Bonsai Bonanza
http://www.BonsaiBonanza.com
Unfortunately that post is for a Linux guest.
I have a Red Hat host with a Windows guest.
How about this... half way down is some params to try:
http://communities.vmware.com/message/7730#7730
The reference is a little off, but the hint was good. Once I had more
specific keywords, I found other articles discussing those parameters.
Putting
host.noTSC = "TRUE"
in /etc/vmware/config appears to have done the trick.