From: "Alexander Vallens" <avallens@archenergy.com>
To: xen-devel@lists.xensource.com
Subject: Re: domU clock over 23s off
Date: Mon, 13 Nov 2006 15:49:23 -0700 [thread overview]
Message-ID: <4558F673.7030501@archenergy.com> (raw)
I'm encountering similar issues on the current release of SuSE 10.1 on a
dual duo-core Opteron system. He this issue ever been fixed?
Thanks!
Alexander
On Feb 26, Keir Fraser wrote:
> >I have rather new installation of xen, dom0 is running ntpd and is
> >perfectly in time. All domU's are ~23s in future. Running ntpd on
> >the domU's seem to have no effect, /proc/sys/xen/independent_wallclock
> >appears to have no effect. I'm running xen-unstable and 2.6.16-rc4
> >in AMD64 box.
>
> Booting the domU's with 'independent_wallclock' as a command-line
> parameter, and then running a standard vendor ntp init script (usually
> ntpdate followed by starting ntpd) certainly *should* have fixed the
> domU time problem.
--
Alexander Vallens
System Administrator
Architectural Energy Corporation
http://www.archenergy.com
Voice: 303-459-7463
Fax: 303-444-4304
next reply other threads:[~2006-11-13 22:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-13 22:49 Alexander Vallens [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-26 10:07 domU clock over 23s off Saku Ytti
2006-02-26 10:20 ` Saku Ytti
2006-02-26 10:21 ` Saku Ytti
2006-02-26 14:47 ` Keir Fraser
2006-02-26 15:47 ` Keir Fraser
2006-02-26 15:51 ` Saku Ytti
2006-02-26 15:52 ` Saku Ytti
2006-07-12 9:00 ` Harald Koenig
2006-07-12 9:25 ` Keir Fraser
2006-07-12 9:56 ` Harald Koenig
2006-07-12 10:42 ` Keir Fraser
2006-07-12 13:37 ` Harald Koenig
2006-07-12 13:43 ` Saku Ytti
2006-07-12 19:46 ` Harald Koenig
2006-07-13 8:17 ` Keir Fraser
2006-07-13 10:05 ` Harald Koenig
2006-02-26 23:55 ` James Henderson
2006-02-27 6:19 ` Saku Ytti
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=4558F673.7030501@archenergy.com \
--to=avallens@archenergy.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.