This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-users] Domains do not shut down or reboot cleanly since upgrade

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Domains do not shut down or reboot cleanly since upgrade to 3.2-1
From: Andy Smith <andy@xxxxxxxxxxxxxx>
Date: Mon, 23 Feb 2009 21:45:01 +0000
Delivery-date: Mon, 23 Feb 2009 13:46:38 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <8301C76F-2DEB-43E8-8EA2-F7A8637B58C2@xxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Openpgp: id=BF15490B; url=http://strugglers.net/~andy/pubkey.asc
References: <7207d96f0902212347v66d3b841i59f95a9335ea1a97@xxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D0162C874@trantor> <8301C76F-2DEB-43E8-8EA2-F7A8637B58C2@xxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.13 (2006-08-11)

On Sun, Feb 22, 2009 at 01:12:28PM +0100, Philipp Schmid wrote:
> On Feb 22, 2009, at 12:36 PM, James Harper wrote:
> >There is a bug in 3.3.1 that comes about when you have more than
> >one  CPU and you restrict Dom0 to one CPU by putting "(dom0-cpus
> >1)" in your config file. The symptoms are that the domain won't
> >shut down until  you do an 'xm start' again, and even then bits
> >of it hang around in the hypervisor.
> >
> >I'm not sure if that bug existed in 3.2 though.
> It seems so:
>       http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1326

Well if allowing dom0 to use all CPUs avoids this problem then
that's what I'll do.

I guess we'll see after the next reboot, though I don't know when
that will be.


Attachment: signature.asc
Description: Digital signature

Xen-users mailing list