From: Saku Ytti <saku+xen-devel@ytti.fi>
To: James Henderson <his_jimboness@yahoo.ca>
Cc: xen-devel@lists.xensource.com
Subject: Re: domU clock over 23s off
Date: Mon, 27 Feb 2006 08:19:27 +0200 [thread overview]
Message-ID: <20060227061927.GA5525@mx.ytti.net> (raw)
In-Reply-To: <44023FF2.9000806@yahoo.ca>
On (2006-02-26 16:55 -0700), James Henderson wrote:
> Hello,
>
> In Xen 2.0.7 I've had clock issues in domU when using OpenNTPD in dom0.
> When I switched to "legacy" ntpd the clocks went back in sync.
>
> It doesn't sound like your server has this particular problem, but I
> thought I'd mention it in case you're running OpenNTPD.
thanks for the tip, bit indeed I'm using original NTPD.
> -James
>
> Saku Ytti wrote:
> > Hey,
> >
> > 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.
> >
> > Any tip would be appricated.
> >
> > Thanks,
>
--
++ytti
next prev parent reply other threads:[~2006-02-27 6:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-13 22:49 Alexander Vallens
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=20060227061927.GA5525@mx.ytti.net \
--to=saku+xen-devel@ytti.fi \
--cc=his_jimboness@yahoo.ca \
--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.