wmoran at potentialtech.com
Wed Jan 14 06:30:31 PST 2009
In response to scuba at centroin.com.br:
> I'm facing some strange behavior with an skew in the system clock.
> The hardware is a Dell PowerEdge 2950III, running two instances of
> FreeBSD 7.0-RELEASE-p5 - amd64 over an ESXi hipervisor.
> To both were allocated 4 processors and 4 GB of RAM, and dmesg for
> both are identical.
> I'm using clockspeed to synchronize the clock, but just one of
> them is delaying the clock a lot.
I doubt that clockspeed will ever work for you. VMWare seems to "pause"
virtual machines when they're not doing anything in order to allocate
CPU for other running VMs.
> The hardware clock is ok as far as the other virtual machine.
> Where should I start to investigate?
For "supported" OS (i.e. Windows/Linux) VMWare provides special programs
to keep the clocks in sync. I expect this is because VMWare knows that
they mangle the clock in such a way that typical clock management
software will never be able to keep it in sync. One problem is that
most clock synching software assumes that drift is relatively constant
(and clockspeed seems to be the same) but clock drift in a virtual
machine is _anything_ but constant.
Unfortunately, VMWare has no love for FreeBSD.
We've been able to keep clocks in sync by adding a cronjob that runs
ntpdate every minute or so. Seems draconian, but it gets the job done.
More information about the freebsd-questions