similar to: Bug#744930: kernel bug

On 2012-12-11, Debian Bug Tracking System wrote: > #674907: shifts the clock by 50 minutes unexplicably under a Xen dom0 > > It has been closed by Bastian Blank <waldi at debian.org>. What about us poor users on Debian squeeze? Or worse, about the upcoming wheezy release? Is there the possibility to backport this fix to s-p-u? Should I ask release.debian.org for a freeze

Whoops, wrong recipient. On Thu, Jun 10, 2010 at 05:54:28PM +0200, Bastian Blank wrote: > I'm currently thinking about which version of Xen supporting in Squeeze. > There are two possibilities: 3.4 and 4.0. 3.4 is currently in testing > and unstable, 4.0 is in experimental. > > Xen 3.4 > ======= > Pros > - Proofed to be stable > Cons > - NUMA-mode only opt-in,

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-1 Severity: grave Tags: squeeze upstream Some newer hardware components (it is unclear what exactly causes the issue) render xen-hyervisor unusable as it crashes immediately after boot for the Debian out-of-box configuration. This results in a system rebooting all over again if the hypervisor is choosen as default stanza to be booted by grub

xm save lenny3 /tmp/lenny3.save The guest console says: Suspending xenbus... and detaches. Restore the guest (paused to attach its console before continuing): xm restore -p /tmp/lenny3.save xm console lenny3 xm unpause lenny3 The console starts spewing out "BUG: recent printk recursion" and the domain spins until destroyed. The same thing happens on (live or not) migration. The

On Wednesday 13 September 2006 16:48, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > #387238: xen-hypervisor: Xen hypervisor reboots when scrubbing ram message > is reached: confirmed on AMD64 and i386, which was filed against the > xen-hypervisor-3.0.2-1-i386 package. Hi Bastian, My conclusion is the same. I think xen-hypervisor

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

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-1 Severity: serious Tags: squeeze Hi there! Upgrading from Lenny to Squeeze left my box with xen-hypervisor-3.2-1-amd64 installed, and I had to "apt-get install xen-hypervisor-4.0-amd64" manually to have it installed after a dist-upgrade. This for sure, isn't the expected behavior. Also, after the dist-upgrade, I did: apt-get

Package: src:xen Version: 4.1.3-4 Severity: serious The bzimage loader used in both libxc and the hypervisor lacks XZ support. Debian kernels since 3.6 are compressed with XZ and can't be loaded. Support for XZ compression was added in changeset 23002:eb64b8f8eebb somewhere last year. Bastian -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990,

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-4 Severity: important Tags: patch, squeeze We have several recent hardware systems from IBM which have the following problem when booting into hypervisor mode on squeeze (amd64, didn't check i386): [ 8.184733] pci 0000:01:00.0: BAR 6: no parent found for of device [0xfffe0000-0xffffffff] [ 8.213235] Initramfs unpacking failed: junk in

Package: xen Version: 4.0.1-1 Severity: serious User: debian-python at lists.debian.org Usertag: python2.6 The package build-depends on python2.5-dev, which is not the default python version for squeeze. The package should be rebuilt with python2.6, either build-depending on python-dev (recommended) or python2.6-dev.

Package: xen-utils-common Version: 3.4.2-1 Severity: important File: /etc/init.d/xend Tags: patch Hello, /etc/init.d/xend assume xenfs is present and doesn't start xend if not. This dirty patch makes xend start and XEN being operationnal with old flavour xen kernels. I use 2.6.31.5 with forwarded ported Xen 2.6.18 dom0 kernel patch but it should work with debian's 2.6.26 ---

Package: xen-hypervisor-4.0-amd64 Fresh install of squeeze beta amd64 System is a Thinkpad X61s with L7500 CPU Windows 7 is on the box, the Thinkpad tools on Windows 7 say VMX is present Followed the squeeze dom0 instructions at: http://wiki.debian.org/Xen aptitude -P install xen-hypervisor-4.0-amd64 linux-image-xen-amd64 xen-tools mv -i /etc/grub.d/10_linux /etc/grub.d/50_linux update-grub2

Processing commands for control at bugs.debian.org: > unarchive 649141 Bug #649141 {Done: Bastian Blank <waldi at debian.org>} [xen-hypervisor-4.0-amd64] xen-hypervisor-4.0-amd64: live migration fails with invalid opcode due to nonstop_tsc Unarchived Bug 649141 > End of message, stopping processing here. Please contact me if you need assistance. -- 649141:

On Sun, Dec 11, 2011 at 06:03, Debian Bug Tracking System <owner at bugs.debian.org> > ---------- Forwarded message ---------- > From:?Bastian Blank <waldi at debian.org> > > This is no bug, but actually documented. You can't migrate systems to a > cpu with lower capabilities. Out of interest, where is this documented? The debian examples would seem to indicate you

Package: xen-hypervisor-3.2-1-amd64 Version: 3.2.1-2 Severity: serious After noting that this version supposedly loads bzImage kernels: | xen-3 (3.2.1-2) unstable; urgency=low | | * Use e2fslibs based ext2 support for pygrub. (closes: #476366) | * Fix missing checks in pvfb code. | See CVE-2008-1952. (closes: #487095) | * Add support for loading bzImage files. (closes: #474509) | *

Processing commands for control at bugs.debian.org: > found 599161 4.0.1-5.5 Bug #599161 {Done: Bastian Blank <waldi at debian.org>} [src:xen] xen-linux-system-2.6.32-5-xen-amd64: Clock moved forward 50 minutes, caused Xen HVM domU restart Bug #674907 {Done: Bastian Blank <waldi at debian.org>} [src:xen] shifts the clock by 50 minutes unexplicably under a Xen dom0 Marked as found

Package: xen-utils-3.2-1 Version: 3.2.0-4 Severity: important Tags: patch pygrub uses tools/libfsimage to read a guest filesystem. Unfortunately the grub derived code does not support 256 byte inodes. Grub itself has been patched (see #463236 and #463123) and this patch has now been applied to the upstream Xen tree. See <http://xenbits.xensource.com/staging/xen-unstable.hg?rev/c777e572a467>

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-1 Severity: grave Tags: squeeze sid Justification: renders package unusable -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-xen-amd64 (SMP w/1 CPU core) Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8

Your message dated Fri, 28 May 2010 10:02:57 +0000 with message-id <E1OHwP3-0007aW-JR at ries.debian.org> and subject line Bug#583283: fixed in xen-3 3.4.3-1 has caused the Debian Bug report #583283, regarding udev - Weird behaviour with device names including a slash 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

Package: xen-hypervisor-4.0-i386 Version: 4.0.1~rc3-1 Severity: critical Tags: upstream patch Justification: breaks the whole system Using 2.6.32 and xen 4.0, balloon driver crash Upstream patch seems to be available : http://lists.xensource.com/archives/html/xen-devel/2010-06/msg00601.html Thanks -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500,