RE: Setting the date not working in xen

RE: Setting the date not working in xen

[Ian Pratt]

> echo 1 > /proc/sys/xen/independent_wallclock
> ntpdate ntp0.oleane.net

independent_wallclock=1 on the kernel command line should fix this too.

Should we change the default? I guess today's common usage model for Xen
has worked out a little differently from what we imagined way back, and
some of the defaults are probably wrong.

Ian

Re: RE: [Xen-users] Setting the date not working in xen

[Keir Fraser]

On 29 Jul 2005, at 12:19, Ian Pratt wrote:

>> echo 1 > /proc/sys/xen/independent_wallclock
>> ntpdate ntp0.oleane.net
>
> independent_wallclock=1 on the kernel command line should fix this too.
>
> Should we change the default? I guess today's common usage model for 
> Xen
> has worked out a little differently from what we imagined way back, and
> some of the defaults are probably wrong.

If this is going to be the default (ntp in every domain) then I won't 
bother modifying xenlinux to propagate domain0 adjtime statistics to 
Xen: it's tedious and pointless if noone is going to use it. But 
slaving domU clocks makes sense to me -- perhaps it's just an issue of 
user education/awareness?

  -- Keir

Re: Setting the date not working in xen

[Shahzad Chohan]

On 7/29/05, Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> wrote:
> > echo 1 > /proc/sys/xen/independent_wallclock
> > ntpdate ntp0.oleane.net
> 
> independent_wallclock=1 on the kernel command line should fix this too.
> 
> Should we change the default? I guess today's common usage model for Xen
> has worked out a little differently from what we imagined way back, and
> some of the defaults are probably wrong.
> 
> Ian


I think we should change the defaults. Its quite common to use
ntpdate. Does it make a lot of difference if the change is made, what
does it affect?

In addition to this I'd say alos include iptables in the xenU kernel
build, I feel its quite a necessity. Yes it might make the kernel
larger but does that really create aproblem in todays hardware world.

Shaz

Re: [Xen-users] Setting the date not working in xen

[Nicholas Lee]

On 7/29/05, Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> wrote:
> independent_wallclock=1 on the kernel command line should fix this too.
> 
> Should we change the default? I guess today's common usage model for Xen

No. The hardware time and syncing this to UTC is a function of the
system, not the instances.  Why have n ntpd daemons running when one
is sufficent?

I think "independent_wallclock=1" should be the special case, when
someone wants to change the instance's view of UTC.

Personally I've simply removed the ntpdate/ntpd package from my domU
init packages.

-- 
Nicholas Lee
http://stateless.geek.nz
gpg 8072 4F86 EDCD 4FC1 18EF  5BDD 07B0 9597 6D58 D70C