similar to: Bug#387238: marked as done (xen-hypervisor: Xen hypervisor reboots when scrubbing ram message is reached: confirmed on AMD64 and i386)

Processing commands for control@bugs.debian.org: > reassign 387238 xen-hypervisor-3.0.2-1-i386 Bug#387238: xen-hypervisor: Xen hypervisor reboots when scrubbing ram message is reached: confirmed on AMD64 and i386 Warning: Unknown package 'xen-hypervisor' Bug reassigned from package `xen-hypervisor' to `xen-hypervisor-3.0.2-1-i386'. > -- Stopping processing here. Please

Your message dated Sat, 10 Dec 2011 20:00:59 +0100 with message-id <20111210190059.GG15557 at wavehammer.waldi.eu.org> and subject line no bug has caused the Debian Bug report #649141, regarding xen-hypervisor-4.0-amd64: live migration fails with invalid opcode due to nonstop_tsc to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it

Your message dated Sat, 14 Apr 2012 19:24:04 +0200 with message-id <20120414172403.GA25566 at wavehammer.waldi.eu.org> and subject line meta-packages available has caused the Debian Bug report #606589, regarding xen-linux-system-2.6.32-5-xen-amd64 doesn't upgrade from xen-linux-system-2.6.26-2-xen-amd64 to be marked as done. This means that you claim that the problem has been dealt

Your message dated Fri, 06 Sep 2013 09:09:48 +0100 with message-id <1378454988.3057.2.camel at dagon.hellion.org.uk> and subject line Re: [Pkg-xen-devel] Bug#710522: Problem found has caused the Debian Bug report #710522, regarding xen-hypervisor-4.1-amd64: Boot hang with Linux 3.2+Xen, works with linux 2.6.32+Xen or 3.2 raw to be marked as done. This means that you claim that the problem

Your message dated Thu, 08 Sep 2011 14:48:50 +0000 with message-id <E1R1fuM-0008SF-9f at franck.debian.org> and subject line Bug#639839: fixed in logcheck 1.3.14 has caused the Debian Bug report #639839, regarding amavisd-new: logcheck "Passed: CLEAN|SPAM" doesn't work because mail-id can contain "-" to be marked as done. This means that you claim that the problem

Your message dated Sun, 31 Aug 2008 19:32:06 +0000 with message-id <E1KZsec-00064d-FQ at ries.debian.org> and subject line Bug#474239: fixed in logcheck 1.3.0 has caused the Debian Bug report #474239, regarding spamassassin: spamd logcheck file doesn't work with shortcircuit enabled to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Your message dated Tue, 24 Jun 2008 20:13:35 +0100 with message-id <20080624191335.GA18136 at lapse.rw.madduck.net> and subject line closed ages ago has caused the Debian Bug report #252165, regarding postfix: Messages from queuemanager flood logcheck 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

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

Your message dated Sat, 06 Apr 2013 13:00:07 +0000 with message-id <E1UOSj1-0002As-63 at franck.debian.org> and subject line Bug#693137: fixed in swift-plugin-s3 1.7-1 has caused the Debian Bug report #693137, regarding ITP: swift-plugin-s3 -- swift3 (S3 compatibility) middleware plugin for swift to be marked as done. This means that you claim that the problem has been dealt with. If this

Your message dated Sun, 10 Aug 2014 12:00:17 +0000 with message-id <E1XGRnN-0007ak-6G at franck.debian.org> and subject line Bug#718898: fixed in xen 4.4.0-1 has caused the Debian Bug report #718898, regarding coreutils: cut no longer works with newline as delimiter 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

Your message dated Fri, 29 Aug 2014 13:26:07 +0000 with message-id <20140829132607.GD4202 at shell.waldi.eu.org> and subject line Xen 3.0 unsupported has caused the Debian Bug report #728295, regarding xen: Issues with Networking on virtual hosts with Xen.3.0.3-1 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

Your message dated Fri, 29 Aug 2014 13:33:00 +0000 with message-id <20140829133300.GB4246 at shell.waldi.eu.org> and subject line xend support gone has caused the Debian Bug report #491660, regarding xen-utils-common: should allow local unix connections 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

Your message dated Sun, 02 Mar 2014 18:42:06 +0000 with message-id <E1WKBKw-0004SD-Mw at franck.debian.org> and subject line Bug#740517: Removed package(s) from unstable has caused the Debian Bug report #710650, regarding xen-api: FTBFS: gcc: error: /home/blank/debian/xen/releases/xen/xen-4.2.1/debian/build/build-utils_amd64/tools/ocaml/libs/xc/../../../../tools/libxc/libxenctrl.so: No such

&gt; If possible it might be interesting to first try the 4.6 hypervisor in&gt; Stretch, I suspect the xen-hypervisor-4.6-amd64 package will just install&gt; on Jessie with no issues since it has no dependencies and you don't need&gt; the userspace tools just to check if it boots.Hey there,I can confirm the issue with new Intel i7-6700 Quad-Core Skylake CPUs and I'm also

Package: xen-hypervisor-3.0.2-1-i386 Version: 3.0.2-3+hg9762-1 Followup-For: Bug #387238 This happens on a PIII as well. Looks similar to an earlier bug report I filed (bug #385934). -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Shell:

Hello, my latest try : X11 starts up and freeze with a black screen. I've updated the nvidia package to 195.36.31-5. ii nvidia-glx 195.36.31-5 ii nvidia-kernel-2.6-xen-amd64 195.36.31+1 ii nvidia-kernel-2.6.32-5-amd64 195.36.31+2+4+2.6.32-24 ii nvidia-kernel-2.6.32-5-xen-am 195.36.31+1+2+2.6.32-21 ii nvidia-kernel-common 20100522+1 ii nvidia-kernel-dkms

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

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

Hi! Make scrub_heap_pages() print from where to where it scrubs pages. Signed-off-by: Christoph Egger <Christoph.Egger@amd.com> This patch uncovers a strange behaviour on 32bit. On 64bit I get this: (XEN) Scrubbing Free RAM 0xffff830000100000 -> 0xffff83003fff0000: ....done. On 32bit I get this: (XEN) Scrubbing Free RAM 0xffc00000 -> 0xdefb0000:

I''m still having problems with 2.0.6 hanging after printing its "scrubbing free RAM" message. comparing with normal behavior, it looks like it''s not transferring to dom0. For more data, see my "upgrade going bad" message. I figure this is something pretty obvious which is why I''m not seeing it. ---eric --