When using VMware Server 1.x, I’ve encountered a few guest Virtual Machines, VMs, where the clocks do not advance correctly. What is especially frustrating about this is that frequently the clocks in the other guest VM’s on the same host are operating correctly. I’ve not yet determined what causes the inconsistency across the guest VM’s, but overtime, I’ve found a few tricks to work-around this issue.
Trick #1 — Host OS power management may be causing the host to update the clock incorrectly, tell the VMware server software the real clock speed of the cpus by modifying the config.ini.
Add the following entries and restart the vmware authorization server
- host.cpukHz = “30000000″ (this example is for a 3 GHZ system)
- host.noTSC = “TRUE”
- ptsc.noTSC = “TRUE”
On windows the default location of the VMware config.ini is C:\Documents and Settings\All Users\Application Data\VMware\VMware Server
On Linux this file is in /etc/vmware/config
Trick #2 — set the VMware Tools Clock Synchronization to update more frequently by editing the .vmx file and adding
- tools.syncTime = “TRUE”
- tools.syncTime.period = “1″ (this is for a 1 second update)
A word of caution, If you use Trick #2 and later you attempt to convert the VMWare Server VM to ESX , then you may have to comment out or remove these items
from the .vmx file. At least one version of VMWare converter did not create a VM that I could use in ESX, until I had removed those items prior to running the converter.