Oops, Sent to Tim personally :-(, sending again
On 2/21/07, Tim Post <tim.post@xxxxxxxxxxxxxxx> wrote:
Have you also reported this to the fedora-xen lists?
:-( not yet but i am posting this issue there as well
On 2/21/07, Tim Post <tim.post@xxxxxxxxxxxxxxx> wrote:
Sorry for the double bang, doh - I forgot to ask, how far are they
drifting? Is each dom-u an equal distance away from dom-0 on the time
line, or is this a random jitter for each guest?
They gradually increased and this has increased to 9 secs now. There
are 4 DomU and atm they are ahead of Dom0 by 7, 9, 8, 9 secs.
On 2/21/07, Tim Post <tim.post@xxxxxxxxxxxxxxx> wrote:
On Wed, 2007-02-21 at 09:31 +0100, Ulrich Windl wrote:
> On 20 Feb 2007 at 21:07, Nadeem Shahbaz wrote:
>
> > Hi,
> > I am facing problem in sync time within DomU with Dom0. After gone
> > through mailing lists, I have set /proc/sys/xen/independent_wallclock
> > to 0. But still DomU are not syncing their time :-S Machine using
>
> Then you missed my messages on how it actually did work. I think 0 is the
default.
> So if the default is bad four you, try a change!
0 is the default, meaning ! independent wall clocks. I don't see how
altering this value to 1 can help solve his issue? While I do appreciate
and employ your problem solving method frequently I don't think it
applies here...
According to the previous mail list, what I understand, if
/proc/sys/xen/independent_wallclock is set to 0, all DomU will sync
their time with Dom0. And most interesting thing is that we have
another machine with same xen configuration and its DomU are sync with
Dom0. We did try to set independent_wallclock to 1 and running ntp
client at each DomU to sync time but it didnt help either as they
drift ~500ms
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|