similar to: xen.independent_wallclock

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

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

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.

Hi all, I can''t find any good talk about this subject and would like some insights and advices on the cache side in xen. I discovered that a domO power outage can lead to a severe filesystem corruption of the domUs. The domO is a dual disk dell server with a PERC controler in writethrough cache mode, the disk cache is disabled, the scheduler in the domO/domU is NOOP, the domO is holding

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, I''ve been building up a new HA system, running Xen on DRBD devices. Configuration this applies to: Debian Lenny xen-linux-system-2.6.26-2-xen-686 package |**|drbd8-modules-2.6.26-2-686 drbd8-modules-2.6.26-2-xen-686 As I''ve been building the system, I ran into an interesting problem, with two symptoms: 1. running VMs would come back up after a reboot, but would hang on

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 -

Hello. Is it possible to run russian win98 programs under current wine, and get russian input and output? If yous, how to setup this? My desktop is russian, I have both koi8-r and unicode fonts installed. Last time I tried wine some months ago (maybe a year), and all russian output of the programs was unreadable - it looked like second byte of unicode characters was just set to zero. Thanks

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 >

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

Hello, I see the new Xen packages now really in Sid and even in Lenny on packages.debian.org: http://packages.debian.org/search?keywords=linux-image+xen+amd64&searchon=names&suite=testing&section=all http://packages.debian.org/lenny/xen-linux-system-2.6.26-1-xen-amd64 Does this mean there is now official Xen amb64 and dom0 support in Lenny? I am running it now for a while without

Hi I have upgraded my Dom0 from lenny to sqeeze and xen to 4.0 after that there were some errors when i tried to reboot, but i could fix most of them my dom0 is running fine now, but when i try to start a guest, i get an error: darwin:/# xm create infopool.cfg Using config file "/etc/xen/infopool.cfg". Error: Device 0 (vif) could not be connected. Hotplug scripts not working. i

Hi. I compiled the xen binaries and the kernel with the sources. DomO starts without any problems, but when I run domU, it stops and freeze. My domU is a clone of my domO. ___________________________________________ unmounting old /dev unmounting old /proc unmounting old /sys INIT: version 2.86 booting rtc: IRQ 8 is not free. modprobe: FATAL: Error inserting rtc

Since your actually forming the raid on dom-0 and not inside of the guest, there is absolutely no need to load md and associated modules in the guest at all. The guest will just see the volume group you are exporting as a regular sata drive the same size as the vg being exported. I''m guessing the second drive is for swap? Hope this helps Best, -Tim On Mon, 2006-10-23 at 16:36 +1000,

What about idea not to *add* pae versions of xen kernels, but to *replace* non-pae versions with pae versions? Rationale: - not increase in archive size or linux-2.6 package build time, - this will improve compatimility with other distros (consider scenario when running FC or RHEL in domU; these distros do ship only pae xen kernels, according to

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 ?

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