similar to: RE: NTP time issues DomU''s

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

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

Hello everyone, I have Hyper V integration working properly, but needed to do an update to 2.6.18-274.12.1.el5-x86_64. Since then, it no longer works. As discovered previously, one needs to rebuild Hyper V Integration tools due to the kernel panic. http://www.sudonym.com/398/kernel-panic-after-yum-update-centos-with-hyper-v-linux-integration-components Done. But I'm getting an error

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

We've noticed our fully-virtualized KVM guests' time keeps getting faster, despite running ntpd. A quick google reveals this to be a known problem with virtual guests. It seems there are a variety of solutions, some apparently vendor-specific. What is the best practice as of now for KVM guests? * Setting independent_wallclock=1 (or is that a xen-only thing)? * Passing kernel

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

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().

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

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

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

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 -

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

Hello, I''m hiring a XEN virtual machine running Ubuntu at a hosting company. My XEN virtual machine is hosted on a server which has some other VM''s running on it. They all use ubuntu or debian. After a crash sometime last week, the systemclock of my VM is off by an hour (it says 19:49, although it''s 18:49 here now). The other VM''s don''t have

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

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