similar to: Bug#638837: independent_wallclock sysctl has gone away?

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

If independent_wallclock is set to 0, then that means running ''date'' in the domU should provide exactly the same answer as running ''date'' on dom0, right? But this isn''t happening for us. The domU''s are all running minutes behind the dom0 - in one case 16 minutes behind! dom0$ date Tue Jun 27 14:23:01 BST 2006 domU-a$ date Tue Jun 27

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

Hi, using SLES10 I''m unable to synchronize the time of DomU with that of Dom0. There is a persistent offset of about 3 seconds! Here''s a small history (not actual output): remote refid st t when poll reach delay offset jitter rkdvmso1.dvm.kl 192.168.0.11 5 u - 64 1 0.136 -2977.1 0.099 *rkdvmso1.dvm.kl 192.168.0.11 5 u 2 64

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

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, 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 kernel-xen-2.6.19-1.2911.fc6 xen-3.0.3-3.fc6 xen-libs-3.0.3-3.fc6 Please advice to solve this weird problem, Thanks _______________________________________________ Xen-users mailing list

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, guys Recently,I met a problem. Xen''s version: 3.4.3 guest os:redhat 4.8 32bit And xen.independent_wallclock = 1 has been set. The time of guest os change to be fast suddenly, about 2000 second. because the change is too wild, ntp didn''t sync to the ntp server''s time. my application is dependent on the systme time. And this occurs a lot of times. I don''t

The time appears to be perfect inside dom0, however all the domU''s tend to have a slightly faster date which gets further out of sync every day. I''m currently using Xen 3.0.3 with Gentoo Linux, under 3.0.2 I had no problems with domU clocks. Are there any known issues which could cause this? I''d strongly prefer not to run ntpd in every domU, having all domU clocks in

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 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

I don''t want my dom0 to update the clock in my HVM domU. I''ve already disabled network-based time synchronization inside the HVM. I''ve tried setting /proc/sys/xen/independent_wallclock=1 and then restarting xend, but the guest still gets the correct time. Any ideas on how to accomplish this? Steve Brueckner, ATC-NY _______________________________________________

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

This must be documented somewhare but I checked the Xen 3.0 manual and the word "clock" doesn''t even exist in it. I checked the FAQ as well. I am running Xen 3.0.1 and an AMD64 CPU. I found that DOMUs time clock drifts ahead. I installed ntpdate and it reports to change the time but it does not. David _______________________________________________ Xen-users mailing list

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

Hello everyone! I been observing some peculiar time drift on my Xen domains (dom0 and domUs). The time (as returned by timeofday) on my domains drifts at an almost steady rate from the real time ( as read from the time stamp counter ). The drift is so constant that it makes me think there should be some simple explanation for it in the way Xen keeps time. Some info about my set up: guest OS:

Hi, I''m trying to get a PV instance of CentOS 5.7 running on XCP. I have 5.7 running in HVM mode on another box and it works fine but I would like to maximize the VM''s performance. It ultimately boots up ok (without graphics) but starts out with the following warnings: rtc: IRQ 8 is not free rtc: IRQ 8 is not free i8042.c: No controller found. Red Hat nash version 5.1.19.6