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] Re: [Xen-devel] network misbehaviour with gplpv and 2.6.

To: "Fajar A. Nugraha" <fajar@xxxxxxxxx>
Subject: Re: [Xen-users] Re: [Xen-devel] network misbehaviour with gplpv and 2.6.30 / HVM domains not shutting down with Xen 3.4.1-rc6 when dom0-cpus is 1
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Wed, 22 Jul 2009 20:59:04 +0300
Cc: xen-users@xxxxxxxxxxxxxxxxxxx, Nerijus Narmontas <n.narmontas@xxxxxxxxx>
Delivery-date: Wed, 22 Jul 2009 11:00:10 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <7207d96f0907211911w988544dk5af978909dcc7252@xxxxxxxxxxxxxx>
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>
References: <AEC6C66638C05B468B556EA548C1A77D016DDD27@trantor> <771c502a0907210353o49ed1f29i8a0540e0572b5d9f@xxxxxxxxxxxxxx> <7207d96f0907211911w988544dk5af978909dcc7252@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.13 (2006-08-11)
On Wed, Jul 22, 2009 at 09:11:32AM +0700, Fajar A. Nugraha wrote:
> On Tue, Jul 21, 2009 at 5:53 PM, Nerijus Narmontas<n.narmontas@xxxxxxxxx> 
> wrote:
> > Hello,
> > If I set (dom0-cpus 1) in /etc/xen/xend-config.sxp, after I gracefully
> > shutdown domU, the domain stays in ---s- state.
> > Is this fixed in 3.4.1-rc8?
> I don't use 3.4.1, but if I remember correctly this is a bug in 3.2
> (is that the version you're using?)
> I'm using Redhat's 3.1+ and Gitco's 3.3.1 and 3.4.0, with (dom0-cpus
> 1) and dom0_vcpus_pin on xen.gz's grub.conf line, and it works
> correctly.

I _think_ this is not a Xen hypervisor bug, but a dom0 kernel bug:


-- Pasi

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>