Your message dated Sun, 30 Dec 2012 21:02:04 +0000 with message-id <[email protected]> and subject line Bug#599161: fixed in xen 4.0.1-5.6 has caused the Debian Bug report #599161, regarding xen-linux-system-2.6.32-5-xen-amd64: Clock moved forward 50 minutes, caused Xen HVM domU restart to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 599161: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599161 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: xen-linux-system-2.6.32-5-xen-amd64 Version: 2.6.32-21 Severity: important Hi, Did you receive this bug report? I hadn't received a bug ID even though receiving the copy of the original report. Likely because the address it was sent from originally was invalid. ----------------- Hi All, Im running Xen 4.0.1-rc6 Debian squeeze with pvops 2.6.32-21 kernel. Today I noticed (when kerberos to the domain controllers stopped working..) that the clock was 50 minutes out in dom0 -- This caused the HVM windows domain controllers to have the wrong time. I'm not sure if this is a kernel issue or a xen issue, but the only thing related is I can see the following in the kernel log: Oct 2 18:50:33 havhost1 kernel: [623480.977748] Clocksource tsc unstable (delta = -2999660303788 ns) But I also see in the dmesg log that xen is using it's own clock. [ 7.676563] Switching to clocksource xen I can't identify anything else in the logs to indicate when the time might have changed. I have a few other dom0 at the same level that haven't decided to change the time. Can anyone confirm whether xen controls the time or the kernel? Also when I corrected the time in dom0 it was still wrong in HVM domU -- How long does it take for this to propogate? (I rebooted the VM's to correct it immediately). It appears the HVM domU (windows server 2008) unexpectedly shut down at 18:51, after the unstable clocksource error. qemu-dm logs show a reset "reset requested in cpu_handle_ioreq." and xend.log shows a reboot Any other pointers on how to ensure stability of clocks from dom0 to domU HVM hosts (and pv for that matter..) would be appreciated. NTP was running but also appeared to have crashed at the same time. Cheers, Mark -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-xen-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xen-linux-system-2.6.32-5-xen-amd64 depends on: ii linux-image-2.6.32-5-xen-amd 2.6.32-21 Linux 2.6.32 for 64-bit PCs, Xen d ii xen-hypervisor-3.2-1-amd64 [ 3.2.1-2 The Xen Hypervisor on AMD64 ii xen-hypervisor-4.0-amd64 [xe 4.0.1~rc6-1 The Xen Hypervisor on AMD64 xen-linux-system-2.6.32-5-xen-amd64 recommends no packages. xen-linux-system-2.6.32-5-xen-amd64 suggests no packages.
--- End Message ---
--- Begin Message ---Source: xen Source-Version: 4.0.1-5.6 We believe that the bug you reported is fixed in the latest version of xen, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [email protected], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand <[email protected]> (supplier of updated xen package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.8 Date: Wed, 26 Dec 2012 13:18:34 +0000 Source: xen Binary: xen-docs-4.0 libxenstore3.0 libxen-dev xenstore-utils xen-utils-4.0 xen-hypervisor-4.0-amd64 xen-hypervisor-4.0-i386 Architecture: source all amd64 Version: 4.0.1-5.6 Distribution: stable-proposed-updates Urgency: low Maintainer: Debian Xen Team <[email protected]> Changed-By: Thomas Goirand <[email protected]> Description: libxen-dev - Public headers and libs for Xen libxenstore3.0 - Xenstore communications library for Xen xen-docs-4.0 - Documentation for Xen xen-hypervisor-4.0-amd64 - The Xen Hypervisor on AMD64 xen-hypervisor-4.0-i386 - The Xen Hypervisor on i386 xen-utils-4.0 - XEN administrative tools xenstore-utils - Xenstore utilities for Xen Closes: 599161 Changes: xen (4.0.1-5.6) stable-proposed-updates; urgency=low . * Non-maintainer upload, previously discussed with Guido. * Fixes Xen clock long standing issue, eg: fix scale_delta() inline assembly, causing domU offset and possibly leading to crashes (Closes: #599161). Thanks to Ian Campbell <[email protected]> for forwarding the patch to the Debian BTS, and Jan Beulich <[email protected]> for working on an upstream patch. Checksums-Sha1: ca6ca68cce7aa942f5ad2f51b22e3420e655e73e 1450 xen_4.0.1-5.6.dsc d0734ac8b09a3256c7db161f4b204aa8e3804593 70875 xen_4.0.1-5.6.debian.tar.gz 83234840b252a4710a768ab6b4971260c8fde41f 1318404 xen-docs-4.0_4.0.1-5.6_all.deb 76c21dc02a78825ac1c97d92f3a3ca3169767815 690564 xen-hypervisor-4.0-amd64_4.0.1-5.6_amd64.deb 96d454e9be5d161606e222e0e3e0240de715f630 260952 libxen-dev_4.0.1-5.6_amd64.deb 98790cb7d1924e5ba0097389aa8ead61250c6533 24746 libxenstore3.0_4.0.1-5.6_amd64.deb a875574d61ee8e1ced9387401b00cc496b7f15f9 1004874 xen-utils-4.0_4.0.1-5.6_amd64.deb e79351cf9dbae6c29c3bed69b35f1c8642000ad4 21360 xenstore-utils_4.0.1-5.6_amd64.deb Checksums-Sha256: d797899a6a1c2326a66cc80a807ea1b59d45d37924c3e71131db2a43242d69b7 1450 xen_4.0.1-5.6.dsc 955e19f896b7596cf083a95ed4e2bf9cfd81a15384d27ce24c853227a416c4f1 70875 xen_4.0.1-5.6.debian.tar.gz fa34262f0a373cef22ca1aee64a39c041edcf14d5d2009b7f79b366257f265be 1318404 xen-docs-4.0_4.0.1-5.6_all.deb 087c07617dc197221f61f8a200776708ea44eedbd917fe8425db6bc94e550efe 690564 xen-hypervisor-4.0-amd64_4.0.1-5.6_amd64.deb 74689bc10f026ab739646efe695c5e788f02b85fca7ee689a2cec317aef9242d 260952 libxen-dev_4.0.1-5.6_amd64.deb 51b8a1c1ecb0573540cfbcdc24edcfaf8e111ea4685a630301d5a1fb1f774294 24746 libxenstore3.0_4.0.1-5.6_amd64.deb 77d8c662ab9715ef0b7ad5c3e078cf05f2267f191eece99e17089ad4bb34a81a 1004874 xen-utils-4.0_4.0.1-5.6_amd64.deb 6079a0c70b3547eb02b3ad3c35c0d892d612efb423bb45977fc1c65100e75a52 21360 xenstore-utils_4.0.1-5.6_amd64.deb Files: 64803fadb724e015517067667d9ea20e 1450 kernel optional xen_4.0.1-5.6.dsc 2f2e797e2fb3af3ebac096b65318987d 70875 kernel optional xen_4.0.1-5.6.debian.tar.gz 78265efbc4a4863ddea4cdeaf2b2e5be 1318404 doc optional xen-docs-4.0_4.0.1-5.6_all.deb ae58a44a048187a5ca69346915dcbead 690564 kernel optional xen-hypervisor-4.0-amd64_4.0.1-5.6_amd64.deb 2796a321d20ad72e7f273d8a5aa14f91 260952 libdevel optional libxen-dev_4.0.1-5.6_amd64.deb f2093b7c82148f63b53bdf77b6541eef 24746 libs optional libxenstore3.0_4.0.1-5.6_amd64.deb d7839c041e69862932320d427d625b68 1004874 kernel optional xen-utils-4.0_4.0.1-5.6_amd64.deb 89c412561393156cc1e43fb0f7702c87 21360 admin optional xenstore-utils_4.0.1-5.6_amd64.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAlDbAXsACgkQl4M9yZjvmklfKwCg3rU3qXXMd5mkMH6ZJqbjvB6Z 5WwAoMC56g14yA2B4iz3EqJXVnceO+BG =kuem -----END PGP SIGNATURE-----
--- End Message ---
