similar to: independent_wallclock=0, domU''s date is 16 mins behind dom0''s date

We have a Xen 3.0 / Linux kernel 2.6.15 machine with the domU''s configured for shared /home directories. One of the domU''s is an NFS server, exporting /home, and the other domU''s all mount this. It all functions fine, but it''s pretty slow. I tried untarring a recent Linux kernel tarball. On the NFS server domU this takes about 25 seconds. I didn''t

Hi. My domU date is about 75 seconds (and climbing?) behind domU. Tue Feb 21 23:11:31 UTC 2006 - dom0 Tue Feb 21 23:10:16 UTC 2006 - domu Tue Feb 21 18:10:17 EST 2006 - domu domUs'' /proc/sys/xen/independent_wallclock was 0 Set that to 1: echo 1 > /proc/sys/xen/independent_wallclock Still out by about 75 seconds: Tue Feb 21 23:14:32 UTC 2006 - dom0 Tue Feb 21 23:13:17 UTC 2006 -

Hi all, can anybody please explain me what changes if i set independent_wallclock to 1 in dom0. I know that setting it to 1 in domU means that the domU will have his clock running independently from dom0 but I don''t understand what does it means setting it to 1 in dom0. Regards -- Dario Fiumicello _______________________________________________ Xen-users mailing list

Package: xen Severity: important Version: 4.0.1-1 The Xen documentation and Xen Debian wiki describes using independent_wallclock to sync domU clocks against the dom0 clock http://docs.vmd.citrix.com/XenServer/4.0.1/guest/ch04s06.html http://wiki.debian.org/Xen#Possible_problems_and_bugs-1 This sysctl appears to have gone away with squeeze, but the documentation is not updated Time drift is

Hi all, finally I have managed to upgrade to Xen 4.0 (actually it reports Xen 4.1-unstable) and Debian''s Linux kernel 2.6.32-4-xen-amd64. Now I am wondering what happend to independent_wallclock. There is no more /sys/xen and sysctl complains error: "xen.independent_wallclock" is an unknown key Does anybody know more about this? Thanks + best regards, Stephan

Hi all, finally I have managed to upgrade to Xen 4.0 (actually it reports Xen 4.1-unstable) and Debian''s Linux kernel 2.6.32-4-xen-amd64. Now I am wondering what happend to independent_wallclock. There is no more /sys/xen and sysctl complains error: "xen.independent_wallclock" is an unknown key Does anybody know more about this? Thanks + best regards, Stephan

Hello. On kernel from linux-image-2.6.18-6-xen-686, there is /proc/sys/xen/independent_wallclock sysctl that may be used to decoupte domU clock from domO clock. This is needed to run ntp in domU. On kernel from linux-image-2.6.26-1-xen-686, there is no such ioctl. Is that a bug or a feature? Is it possible to decoupte domU clock from domO clock when domU is running on

Hi, I''d be very interested to hear: does anyone have a stable working amd64 machine (in 64bit mode)? if so, which kernel do you use, and which version of xen / hg tree do you use? linux-2.6-xen.hg compiles fine over here, but reboots during boot. so fast I can''t see anything. (sorry, my laptop has no serial port. so I can''t capture a log file.) 2.6.16-rc4-git8 plus

Hello ! Just a quick question about time synchronization between xen dom0 and domUs... We''re running Xen 3.1 64-bit, with 32 and 64 bits linux guests. It''s up since 89 days and the domU''s time is around 5 minutes behind the dom0, which is updated via ntpdate... Any idea why it doesn''t sync the guests even that /proc/sys/xen/independent_wallclock is 0 ?

Hi all, where can I set the date in domU. ''ntpdate -u ...'' works but dosn''t set the date. date MMDDhhmm has also no effect. What can I do? -- cu Roland Kruggel  mailto: rk-liste@gmx.de System: Intel 3.2Ghz, Debian etch, 2.6.15, KDE 3.4 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

Hi All, I have just started looking at the code for Xen so please bear with me. A domU Linux kernel running with independent_wallclock=1 seems to sync its time with dom0 after every "xm unpause" (obviously preceded by an "xm pause"). I don''t see where the xtime variable is being updated after an "xm unpause", i.e., domain_unpause_by_systemcontroller().

Hi all, I''m experiencing problems with time: after I sync time both into dom0 and dom1 with public ntp servers, times are not the same. Do you have the same problem? Thanks Marco _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi folks, I did not find anything about passing kernel arguments to a domU kernel. How is the syntax for the config file in Xen 2.x? Just adding the argument to the kernel line does not work. I need to pass independent_wallclock=1 to my domU kernels. Thanks for any hint or help! Dirk _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

I think it''s perfect the way it is. Run NTP in dom0, all the domU''s then have synchronized time. I can still set timezones on all of these boxes independantly. Timezone has nothing to do with NTP synchronization. Tim:> > yeah, i''m already doing that, I was just saying, it *seemed* > like they were getting their time from domain0, and weren''t >

While in the upstream kernel I''m unable to find any use of XENPF_settime (and the DOM0_SETTIME alias of it) at all, in the 2.6.18 tree (and the forward ports of it) the function gets used only when ntp_synced() returns true (and - that''s minor - when independent_wallclock is not set). It would however seem to me that this doesn''t cover the case where the host clock gets

Hi list, one and hopefully last strange thing I figured out ist the systime of my guests. Dom0 uses ntp for time syncronisation. I set the time on my guests manually but after reboot any machine (Windows server, XP, Freebsd, even PV Machines like ubuntu) all run local time - 2 hours. /proc/sys/xen/independent_wallclock is set to 0 so actually the time should be set by dom0...(?) Any

Hi all, I am running Scientific Linux 5.1 (rhel 5.1 compatible) 64bit on a 2x4core system with 16 gb ram with 3 Scientific Linux 4.6 (rhel 4.6 compatible) guests an one Scientific Linux 5.1 guest. I do not run ntp on the guests but only on dom0. One specific Scientific Linux 4 domU always looses time synchronization with dom0. All the others SL4 and the SL5 domUs remain synchronized. There

My dom0 systems all run ntpd to keep their clock synchronized, and I just noticed my domU systems all have a little different clock, and that happens right after boot. IE, right after xm create domU, I did a quick''n''dirty check this way: luca@dom0 ~ $ ssh domU "uptime; date"; date Password: 16:11:31 up 0 min, 0 users, load average: 0.43, 0.12, 0.04 Thu Dec 8

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

Hello, I know, often asked, often discussed .. No recommendation from Citrix. What is the better solution? 1) use ntp in the XEN host and synchronize the guests with the clock running on the control domain (independent_wallclock=0, what the default is) 2) or use ntp in host and guest (and independent_wallclock=1) I ask, because the XEN host (bare metal) has a more stable clock and if the ntp