You might have missed the second part of the documentation, which talks about
the option "pref.timeLagInMilliseconds". One time sync does not kick in if the
error is within 1000 milliseconds. This threshold can be controlled using
"pref.timeLagInMilliseconds". Could you please check this?
Thanks,
Ravindra
________________________________
From: Patrick Hemmer <open-vm-to...@stormcloud9.net>
Sent: Monday, April 03, 2017 2:16 PM
To: open-vm-tools discussions
Subject: Re: Time not syncing after VMotion
�Unfortunately it does not. All this document does is instruct in usage of
ntpd. Ntpd takes too long to adjust the clock. It takes to long to even detect
that the clock is out of sync and needs to be fixed.
This functionality is supposed to be part of the vmware tools for exactly this
issue. For example, see this document:
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1189
> Time is resynchronized when you migrate the virtual machine using vMotion,
> take a snapshot, restore to a snapshot, shrink the virtual disk, or restart
> the VMware Tools service in the virtual machine (including rebooting the
> virtual machine).
-Patrick
On 2017/4/3 16:35, Ravindra Kumar wrote:
Hi Patrick,
Could you please see if�https://kb.vmware.com/kb/2108828�helps?
Thanks,
Ravindra
________________________________
From: Patrick Hemmer
<open-vm-to...@stormcloud9.net><mailto:open-vm-to...@stormcloud9.net>
Sent: Friday, March 31, 2017 2:52 PM
To:
open-vm-tools-discuss@lists.sourceforge.net<mailto:open-vm-tools-discuss@lists.sourceforge.net>
Subject: Time not syncing after VMotion
�
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<mailto:open-vm-tools-discuss@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/open-vm-tools-discuss
------------------------------------------------------------------------------
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
