WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] domU crashing, trying to determine why

To: Pasi Kärkkäinen <pasik@xxxxxx>
Subject: Re: [Xen-devel] domU crashing, trying to determine why
From: micah anderson <micah@xxxxxxxxxx>
Date: Sun, 02 Jan 2011 22:41:24 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 11 Jan 2011 02:46:34 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110102183909.GG2754@xxxxxxxxxxx>
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: <87mxnka0yg.fsf@xxxxxxxxxxxxxxxx> <20110101214106.GE2754@xxxxxxxxxxx> <87ipy89lu3.fsf@xxxxxxxxxxxxxxxx> <20110102125913.GF2754@xxxxxxxxxxx> <8762u79nph.fsf@xxxxxxxxxxxxxxxx> <20110102183909.GG2754@xxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Notmuch/0.3.1-93-g3ec9d24 (http://notmuchmail.org) Emacs/23.2.1 (i486-pc-linux-gnu)
On Sun, 2 Jan 2011 20:39:09 +0200, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
> On Sun, Jan 02, 2011 at 01:15:22PM -0500, micah anderson wrote:
> > On Sun, 2 Jan 2011 14:59:13 +0200, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
> > > On Sat, Jan 01, 2011 at 07:43:32PM -0500, micah anderson wrote:
> > > > On Sat, 1 Jan 2011 23:41:06 +0200, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
> > > > > On Sat, Jan 01, 2011 at 02:16:55PM -0500, Micah Anderson wrote:
> > > > > > 
> > > > > > I'm having a domU that is regularly crashing, without any obvious 
> > > > > > reason
> > > > > > why. I set 'on_crash=preserve' to try and get a crash to try and get
> > > > > > some clues, but what I got doesn't too obvious to me. I was hoping
> > > > > > someone here would be able to give me some clues. 
> > > > > > 
> > > > > > Thanks for any clues anyone can give! Here is what I managed to eke 
> > > > > > out:
> > > > > > 
> > > > > > root@guillemot:/etc/xen# /usr/lib/xen-3.2-1/bin/xenctx -s 
> > > > > > /boot/System.map-2.6.26-2-xen-686 11 0
> > > > > 
> > > > > So the domU has only 1 vcpu? 
> > > > 
> > > > No, I did this for both vcpus, the second one is below:
> > > > 
> > > 
> > > True, I somehow missed the other one.
> > > Did you check debian bugreports if there are other reports like this? 
> > 
> > I did, but I didn't find anything relevant.
> > 
> 
> Can you list the steps to reproduce the bug/crash? Does it happen every time?
> Does it happen if you have only 1 vcpu for the domU?

There really aren't any steps. I 'xm create' the domain, and then what
seems like a random amount of time later, it crashes. Usually that
random amount of time is somewhere between one week and four weeks, but
I've had it happen twice in a weekend. 

I've got this setup:

vcpus=2
cpus=[1,3]

I really need available CPU power of 2 CPUs, or the machine will be too
underpowered... 

m

Attachment: pgpTV8UkYHDTw.pgp
Description: PGP signature

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel