similar to: Bug#630984: shutdown hangs with xenwatch and reboot being blocked

Package: xen-utils-common Version: 4.0.0-1 Severity: normal Tags: squeeze The host runs (at the time of testing) a single linux-x86 domu (128MB, 1VCPU). When issuing a reboot, everything looks as expected: - domu is saved - xend is stopped - drbd stopped - lvms unmounted - md0..4 stopped and the message "rebooting now" appears, but nothing happens until "INFO: task xenwatch is

Add xs_reset_watches function to shutdown watches from old kernel after kexec boot. The old kernel does not unregister all watches in the shutdown path. They are still active, the double registration can not be detected by the new kernel. When the watches fire, unexpected events will arrive and the xenwatch thread will crash (jumps to NULL). An orderly reboot of a hvm guest will destroy the

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 Jeremy, The below implements the getgeo hook for Xen block devices. Extracted from the xen-unstable tree where it has been used for ages. It is useful to have because it allows things like grub2 (used by the Debian installer images) to work in a guest domain without having to sprinkle Xen specific hacks around the place. Signed-off-by: Ian Campbell <ijc@hellion.org.uk> diff --git

Hi Jeremy, The below implements the getgeo hook for Xen block devices. Extracted from the xen-unstable tree where it has been used for ages. It is useful to have because it allows things like grub2 (used by the Debian installer images) to work in a guest domain without having to sprinkle Xen specific hacks around the place. Signed-off-by: Ian Campbell <ijc@hellion.org.uk> diff --git

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-4 After an upgrade to squeeze I've installed Xen 4.0, but when trying to boot the Xen kernel the boot freezes at the message: Waiting for /dev to be fully populated... Nothing further usually [*] appears after this message, and after a short time the screen becomes blank (and power saves, as if there is no signal) and there appears to be

Processing commands for control at bugs.debian.org: > close 587090 4.1.0~rc6-1 Bug #587090 [xen-utils-4.0] xen-utils-4.0: Exception starting xend ('NoneType' object has no attribute 'rfind') There is no source info for the package 'xen-utils-4.0' at version '4.1.0~rc6-1' with architecture '' Unable to make a source version for version

Hi, I''m trying to install Debian Squeeze as DomU on an openSUSE 11.4 Xen host but fail all the time. I''ve also searched Google and Debian as well as openSUSE resources but haven''t found any hint about my issue :-( First I''ve tried to install it as a paravirtualized guest but when the Debian installer tries to detect the disks I get this: [ 173.233735]

The backport of the xenbus code for the 2.4 kernel changed wait_event_interruptible() into wait_event() into a couple of places it looks to deal with the fact that signals weren''t being blocked. This results in an idle domU showing a load-average of 2, which was messing up some work-management tools. The attached patch blocks all signals for the xenbus and xenwatch daemons, instead.

Processing commands for control at bugs.debian.org: > # reassigning all open bugs reported against versioned xen packages that are no longer in the archive to src:xen > reassign 399073 src:xen 3.0.3-0-2 Bug #399073 [xen-hypervisor-3.0.3-1-i386] xen-hypervisor-3.0.3-1-i386: dom0 crashes with a domU that define more than 6 vdb Warning: Unknown package 'xen-hypervisor-3.0.3-1-i386' Bug

Hello, I''m using my dom0 on a RHLE 4.4 with xen 3.0.4-1. My domUs work on the same O/S, and any virtual disk is composed by 5 files : disk = [

Hi, "Ian Campbell" <ijc at hellion.org.uk> ?rta 2013-10-22 11:17-kor: > On Tue, 2013-10-22 at 11:52 +0200, PASZTOR Gyorgy wrote: > > When you use xl toolstack, you can't reboot domUs. > > When you switch back to xm toolstack, than reboot works again. > > I think the problem with the debian packaged version is the same as in > > this thread: > >

Subject: Re: [CentOS-virt] Xen4CentOS kernel panic on dom0 reboot On Wed, Mar 5, 2014 at 10:17 AM, David Vrabel <david.vrabel at citrix.com>wrote: > > On 05/03/14 15:09, Karl Johnson wrote: > > > I've been using Xen4CentOS for the last 3 months. It's working fine and > > > dom0/domUs are stable but the server does a kernel panic when doing a > > >

Processing commands for control at bugs.debian.org: > user debian-qa at lists.debian.org Setting user to debian-qa at lists.debian.org (was anbe at debian.org). > affects 774889 + xfswitch-plugin Bug #774889 [gdm3] gdm3: fails to upgrade squeeze -> wheezy -> jessie - trying to overwrite /usr/share/gdm/BuiltInSessions/default.desktop Added indication that 774889 affects xfswitch-plugin

This implements a suggestion by Keir to remove the xenbus "ignore state transitions on shutdown" code for kernels without a shutdown callback. Signed-off-by: David Lively <dlively@virtualiron.com> Signed-off-by: Ben Guthro <bguthro@virtualrion.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

I am having an issue getting a DomU to boot properly. There is never any indication of a stop error or kernel panic, it simply hangs after "Starting crond [ OK ]" and never continues. I''ve included my mkinitrd and output from xm create... please help! ##### XENBUS errors ##### XENBUS: Device with no driver: device/vbd/2049 XENBUS: Device with no driver: device/vbd/2050

Processing commands for control at bugs.debian.org: > # reassigning all open bugs reported against versioned xen packages that are no longer in the archive to src:xen > reassign 514918 src:xen 3.3-unstable+hg17961-1 Bug #514918 [xen-utils-unstable] xen-utils-unstable: xend starts with errors Warning: Unknown package 'xen-utils-unstable' Bug reassigned from package

Package: xen-utils-common Version: 3.4.2-3 Severity: normal If one daemon is running but the others are not then the stop script will fail. It should use the pid file for each daemon and try to stop them independently. Note that the fact that Xen shouldn't get into this state is not relevant, daemons do periodically fail, relevant system control scripts should be able to stop them even

Hello! I have testing new xen 4.1.0 with Debian Wheezy. I have an strange problem. When I try to boot the DomU with disks in local img works Ok: disk=[''file:/VMs/plantilla-squeeze-disk.img,xvda1,w'', ''file:/VMs/plantilla-squeeze-swap.img,xvda2,w''] but when I try to boot with the same disk offered with iSCSI: (open-iscsi, login, ...)

Processing commands for control at bugs.debian.org: > tags 630984 + moreinfo Bug #630984 [xen-utils-common] xen-utils-common: shutdown hangs with xenwatch and reboot being blocked Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 630984: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630984 Debian Bug Tracking System Contact owner at