Xen devel - Jul 2005 - Setting the date not working in xen

Hi

I''m trying to set the date in my domU. But it refuses to update
itself, here''s what happens:

[root@rhel-3-ws root]# date
Fri Jul 29 10:44:03 BST 2005
[root@rhel-3-ws root]# date -s "Fri Jul 29 11:44:20 BST 2005"
Fri Jul 29 11:44:20 BST 2005
[root@rhel-3-ws root]# date
Fri Jul 29 10:44:19 BST 2005
[root@rhel-3-ws root]#

Even ntpdate doesn''t force an update.

Does anyone have any idea how to fix this?

Thanks in advance
Shaz
Shaz

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

hello,
> I''m trying to set the date in my domU. But it refuses to update
> itself, here''s what happens:
> 
> [root@rhel-3-ws root]# date
> Fri Jul 29 10:44:03 BST 2005
> [root@rhel-3-ws root]# date -s "Fri Jul 29 11:44:20 BST 2005"
> Fri Jul 29 11:44:20 BST 2005
> [root@rhel-3-ws root]# date
> Fri Jul 29 10:44:19 BST 2005
> [root@rhel-3-ws root]#
> 
> Even ntpdate doesn''t force an update.
> 
> Does anyone have any idea how to fix this?

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

Regards

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Hi

Great that worked, your a star.

Thanks
Shaz

On 7/29/05, Franck <franck@linuxpourtous.com>
wrote:
> hello,
> 
> > I''m trying to set the date in my domU. But it refuses to
update
> > itself, here''s what happens:
> >
> > [root@rhel-3-ws root]# date
> > Fri Jul 29 10:44:03 BST 2005
> > [root@rhel-3-ws root]# date -s "Fri Jul 29 11:44:20 BST
2005"
> > Fri Jul 29 11:44:20 BST 2005
> > [root@rhel-3-ws root]# date
> > Fri Jul 29 10:44:19 BST 2005
> > [root@rhel-3-ws root]#
> >
> > Even ntpdate doesn''t force an update.
> >
> > Does anyone have any idea how to fix this?
> 
> 
> echo 1 > /proc/sys/xen/independent_wallclock
> ntpdate ntp0.oleane.net
> 
> Regards
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> 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

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

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


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

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

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Fri, Jul 29, 2005 at 12:43:00PM +0100, Shahzad Chohan
wrote:
> 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?
Are there situations in which domUs need different times than the
dom0?

If not, what''s the point?  I''d rather ntpdate et all died
immediately.

I don''t want my users running completely pointless software and then
saying they are short on RAM...


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

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

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel