So every time we do a VMotion, our guest clock is off by a few hundred
milliseconds. We do run ntpd, so it eventually corrects itself. But
these time discrepancies can cause problems until ntpd gets around to
fixing things. According to various resources I can find on the
internet, the time is supposed to be synchronized after a few events
happen, such as snapshots, and vmotions.
We have the periodic time sync disabled (though we tried with it
enabled, and it made no difference). We do not have any of the
"time.synchronize.*" options set in the vmx file.
Any idea why the time is not synchronizing? Or how to debug this?
-Patrick
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
open-vm-tools-discuss mailing list
open-vm-tools-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/open-vm-tools-discuss
