Date: Mon, 30 May 2011 10:27:37 +0000 (UTC) From: Janne Snabb <snabb@epipe.com> To: Alex <other@ahhyes.net> Cc: freebsd-xen@freebsd.org Subject: Re: Clock drift issues Message-ID: <alpine.BSF.2.00.1105301003390.62994@tiktik.epipe.com> In-Reply-To: <ad6bd7648ad54a4ce99b1bdb4ee5f8b0@ahhyes.net> References: <ae5912296170b53bbf15afe6fb1b55d7@ahhyes.net> <4DE357AA.3070007@unsane.co.uk> <ad6bd7648ad54a4ce99b1bdb4ee5f8b0@ahhyes.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 30 May 2011, Alex wrote: > The clock is Sync'd though, it should *stay* correct, right? So there is a > bug? My experience is also that the clock is not stable on FreeBSD 8.X guest on Xen and KVM HVM. It is unusable as a ntp server for other hosts and I need to run ntpd to prevent the guest clock from drifting and jumping. Some times I get syslog messages about the time going backwards, which is probably related: calcru: runtime went backwards from 41668 usec to 35093 usec for pid 96767 (bash) I have not tried this with the CURRENT kernel (which has new and configurable event timer infrastructure by mav@). (Linux guests are fine for running ntp server within Xen & KVM.) -- Janne Snabb / EPIPE Communications snabb@epipe.com - http://epipe.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1105301003390.62994>