Hello Martin, > So you are running ntpd in a DomU? This has turned out to be > problematic in the past; there once was a suggestion on this list to set > xen.independent_wallclock=1 in /etc/sysctl.conf. > - Martin
No no, I'm running ntpd on Dom0. (Yeah and I have independent wallclocks on DomUs, syncing with Dom0 using ntp). And... http://www.pool.ntp.org/scores/193.87.160.18/graph/offset.png >From what can I see 'till now guys, it looks like "disable kernel" will do the job (*knocking on wood*), do you see that short linear something that now seems to be trying to achieve X-axis? :) Yeah of course, it may still be just a tooth, but let's wish this problem solved. :D And maybe here comes the reason of "popular" error messages almost every XEN-admin met: "clocksource/0: Time went backwards..." - it looks like XEN-patched kernel generates funny switchback time? The complete solution then seems to be 'disable kernel' in ntp.conf plus 'xen.independent_wallclock=1' in sysctl.conf-s plus ntp-s on DomU-s for DomU-Dom0 time syncing. The second question that comes to my mind then is - why kernel uses different algo for clock and why isn't it fixed yet? %) As it more and more seems to be solved, I would like to thank Dave Hart for the idea of adding 'disable kernel' to ntp.conf. _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
