<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=iso-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Collins,<br>
<br>
Collins Richey wrote:
<blockquote
cite="mid:CAE7CeacxgYpoi5x0DEM+ois0fn8CXjeb-XRK7C1pKMpg9Dqt3g@mail.gmail.com"
type="cite">
<pre wrap="">On Mon, Jul 25, 2011 at 4:59 PM, Jim Ockers <a class="moz-txt-link-rfc2396E" href="mailto:ockers@ockers.net"><ockers@ockers.net></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Unfortunately I forgot to stabilize the system clock, and by the end of the
day the phones were unusuable because the VM system clock/time was wandering
around and even ntpd in the VM refused to work, insisting that it did not
know what time it was.
</pre>
</blockquote>
<pre wrap=""><!---->
When the clock is too far out of sync, ntp will refuese to do
anything. Run ntpdate <clockreferencehost> to force setting the clock,
then you can start ntp successfully.
</pre>
</blockquote>
Yes, this system (based on CentOS 4.3) was already set to run ntpdate
against a reliable clock source at boot-up (from rc.local), and ntpd
was started right after that. Even so, the clock in the VM was so
unstable that ntpd could never stabilize the system time. I think it
wandered around too much. In this case ntpd would never reach stratum
3 and always insisted that it didn't know for sure what the time was.
After I added "clock=pit" to the kernel boot command line then ntpd was
able to stabilize the system clock.<br>
<br>
Jim<br>
<br>
</body>
</html>