[ntp:questions] Timekeeping on Windows 2008r2 VM on Linux QEMU/KVM

Harlan Stenn stenn at ntp.org
Wed Jan 21 23:46:01 UTC 2015


Sander Smeenk writes:
> Quoting Rob (nomail at example.com):
> > > What is actually wrong with running ntpdate to initially sync a clock?
> > The problem is that you give the clock an initial kick that ntpd does
> > not know about, and it tends to have problems correcting that.
> > This sometimes results in the problems you are seeing.
> 
> But i cant use ntpdate is ntpd is still running because the socket/port
> is already bound. But this possibly follows up on your 'the OS might
> keep track of drift/frequencies'-quote at the end of your mail.

That's correct, you cannot and should not change the time if ntpd is
running.

If ntpd is running and your clock is off, then you have some other
problem.

If your clock is slow, you are likely dropping clock interrupts.  But
that has tended to be more of an issue under Linx kernels than anywnere
else.

Have you seen http://support.ntp.org/Support/TroubleshootingNTP ?

H


More information about the questions mailing list