From: Carl Jones <carl@outerloop.net>
To: xen-devel@lists.xensource.com
Subject: domU time drifting
Date: Mon, 13 Dec 2010 13:12:58 +1300 [thread overview]
Message-ID: <AANLkTimP3+Jen1s0=TVhU3LOq--d6AsDkMYW5Z0zMajM@mail.gmail.com> (raw)
Hi,
I am trying to track down the cause of time drifting on our domUs.
We're using various versions of Xen, and various domU kernels.
dom0s all run ntpd and are in sync. No issues there.
dom0s are all running CentOS 5 64bit. domUs run various distributions
(the examples below happen to be Debian and Ubuntu only).
domUs that do not run ntpd tend to drift (both forwards and
backwards). domUs are using clocksource=xen. dom0s are using
clocksource=jiffies.
Some example setups:
Xen: 3.4.3
dom0: 2.6.18.8 x86_64 based on el5 sources
domU: 2.6.30.5 i386
domU uptime: 68 days
dom0: Sun Dec 12 23:45:59 UTC 2010
domU: Sun Dec 12 23:44:48 UTC 2010
Xen: 3.3.1
dom0 2.6.18.8 x86_64 from xen.org
domU: 2.6.33.3 i386
domU uptime: 34 days
dom0: Sun Dec 12 23:51:20 UTC 2010
domU: Sun Dec 12 23:50:39 UTC 2010
Xen: 3.4.3
dom0: 2.6.18.8 x86_64 based on el5 sources
domU: 2.6.30.5 i386
domU uptime: #1 28 days #2 26 days
dom0: Sun Dec 12 23:58:23 UTC 2010
domU #1: Sun Dec 12 23:58:03 UTC 2010
domU #2: Sun Dec 12 23:58:04 UTC 2010
The last example is interesting. Two domUs on the same host have the
same (incorrect) time. Same domU kernel. Different uptime.
I've tried suggestions in bug reports like these:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534978
http://wiki.debian.org/Xen#A.27clocksource.2BAC8-0.3ATimewentbackwards.27
http://my.opera.com/marcomarongiu/blog/2010/08/18/debugging-ntp-again-part-4-and-last
But so far the problem persists.
Is there anything we can do on the host side of things to prevent
domUs from drifting? With clocksource=xen shouldn't the domUs stay in
sync provided the host keeps the correct time?
Please let me know if I can provide further details.
Regards,
Carl
next reply other threads:[~2010-12-13 0:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 0:12 Carl Jones [this message]
2010-12-13 7:11 ` domU time drifting Keir Fraser
2010-12-13 8:02 ` Carl Jones
2010-12-14 20:55 ` Jeremy Fitzhardinge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTimP3+Jen1s0=TVhU3LOq--d6AsDkMYW5Z0zMajM@mail.gmail.com' \
--to=carl@outerloop.net \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).