Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I spent about 2+ weeks in early 2003/2004 trying to get VMware Server to properly keep the time in Sync. I had memorized the VMware whitepaper on the topic, and had followed every possible bit of advice they offered (including not using NTPD) - nothing worked. Eventually just cronned ntpdate to run every minute and that resolved the issue on all our systems.

This, by the way, horrified all our NTPD theoreticians, who made it clear that running ntpdate was going to cause catastrophic things to occur in our Operations environment - but, given that our logs were all getting progressively more and more useless as we were unable to correlate times for events between servers - the worst case scenario (in my mind) had already occurred.

I don't recall any particularly negative side effects as a result of our ntpdate sledgehammer.

I presume things have gotten better in the last 10 years with VMware.



Somewhat.

Years ago, the answer was to run NTP on the host and use VMWare Tools to help ensure that good quality time was served to the clients. That's when the earlier versions of the page at <http://support.ntp.org/bin/view/Support/KnownOsIssues#Sectio... were written.

Since then, that advice has apparently been recanted.

The ultimate problem with any virtualization system is the frequency and accuracy of clock updates to the client, and the loss of clock interrupts.

To the degree you can solve that problem, protocols like NTP can work reasonably well to monitor and correct for various types of known clock issues.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: