Package: xen-linux-system-2.6.26-1-xen-686 Version: 2.6.26-10 Severity: important File: xen-linux-system
When dom0 boots up, all restored domUs (2 x etch and 1 x lenny) have their clocks set to the time when they were restored and their clocks are "frozen" in that time, with following error appearing in all domUs' dmesg: clocksource/0: Time went backwards: ret=b01d2985eb delta=-929476120446 shadow=b00552031d offset=17d7f610 (ret, delta, shadow and offset vary over time) "xm destroy domU && xm create domU.cfg" seems to fix the problem, but only until I reboot/shutdown dom0 again. Manual "/etc/init.d/xendomains restart" doesn't fix the problem, but it doesn't reintroduce it either once the domUs have been manually recreated with xm destroy/create. This happens on every dom0 boot. domU.cfg (Created with xen-tools, other domUs have pretty much similar config. "virtual" is the name of LVM VG.): kernel = '/boot/vmlinuz-2.6.26-1-xen-686' ramdisk = '/boot/initrd.img-2.6.26-1-xen-686' memory = '256' root = '/dev/sda2 ro' disk = [ 'phy:virtual/vm2-swap,sda1,w', 'phy:virtual/vm2-root,sda2,w', ] name = 'domU' vif = [ 'ip=192.168.0.30,mac=00:16:3E:C9:B2:1C' ] on_poweroff = 'destroy' on_reboot = 'restart' on_crash = 'restart' I'm sorry if I filed this bug under the wrong package, but it seemed correct since xen-linux-system covers pretty much everything xen* . Regards, Ivan Savcic -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-xen-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xen-linux-system-2.6.26-1-xen-686 depends on: ii linux-image-2.6.26-1-xen-686 2.6.26-10 Linux 2.6.26 image on i686 ii xen-hypervisor-3.2-1-i386 3.2.1-2 The Xen Hypervisor on i386 xen-linux-system-2.6.26-1-xen-686 recommends no packages. xen-linux-system-2.6.26-1-xen-686 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
