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-devel] Debian Lenny 2.6.26-2-xen-686 crashing as multi-vcpu dom

To: Jan Beulich <JBeulich@xxxxxxxxxx>
Subject: Re: [Xen-devel] Debian Lenny 2.6.26-2-xen-686 crashing as multi-vcpu domU, stack trace
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Fri, 5 Mar 2010 15:12:21 +0200
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 05 Mar 2010 05:12:56 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4B910E870200007800032F92@xxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20100305124709.GA2580@xxxxxxxxxxx> <4B910E870200007800032F92@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Fri, Mar 05, 2010 at 01:00:39PM +0000, Jan Beulich wrote:
> >>> Pasi Kärkkäinen<pasik@xxxxxx> 05.03.10 13:47 >>>
> >Basicly the guest get stuck somehow, and starts to consume all the CPU time 
> >it can get.
> Would seem like you posted the xenctx output only for one of the two
> vCPU-s (which isn't able to acquire xtime_lock as it seems) - the
> question is what the other vCPU is doing then.

Damnit, I didn't realize that.. and now the domU is destroyed/rebooted already..

-- Pasi

Xen-devel mailing list