similar to: independent_wallclock in dom0

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

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

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 all, I have a problem with pci passthrough in xen 3.4.0 (Debian Lenny). I need to pass the audio board (which is 00:1b.0) to the domU, so I do the following: - Put pciback.permissive pciback.hide=(00:1b.0) in dom0 kernel boot options - Put swiotlb=force in domU kernel boot options - Put pci = [ ''00:1b.0'' ] in domU config file - reboot the machine I can see in dmesg the

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 -

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

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

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 everybody! I know this is an ultraknown issue, but in my case i think it is going beyond. As you may guess my domUs clocks go faster or slower They come with the same OS (Centos 5 2.6.18-92.1.18.el5 ) but each of them have a different clock speed. Why? Dom0 does not syncronize domUs : So i watched out looking for any solution.... First attempt: /proc/sys/xen/independent_wallclock = 0

Hi everyone, I have the problem with Xen domU's and timekeeping in dom0. Time in dom0 was incorrect by 5 hours due to wrong timezone assumed. Fixed it by ntpdate ntp.nist.gov. The time on a dom0 was changed. I didn't append xen.independent_wallclock=1 to sysctl.conf thus the time in all domU's was also changed. But THEY DIDN'T "KNOW" THAT! The 'date' output

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

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

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

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 _______________________________________________

Hi, I have a question about the memory layout of the Xen hypervisor, dom0 and domU. *The goal I want to achieve is: I want to show which RAM area is used by hypervisor, which RAM area is used by dom0, which RAM area is used by each domU (PV guest domain). I hope to know the above information when xen is booted as well as when xen is running some domUs. I already know that we can dedicate a fix

Hello, On a xenserver with several (39) domUs, we experience problems with the system clock of the domUs. The clock seems to drift away several seconds up to two minutes from the dom0 clock. We do have set independent_wallclock=0. According to the docs (i.e. http://wiki.xensource.com/xenwiki/InstallationNotes) that way domUs should use the dom0 clock, but apparently that''s not the case.