From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: experienced unstability
Date: Tue, 21 Apr 2009 12:51:11 +0100
Message-ID: <C61371BF.91A4%keir.fraser@eu.citrix.com>
References: <49EDAD52.3040506@web.de>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <49EDAD52.3040506@web.de>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: "jon.hart" <jon.hart@web.de>, "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

On 21/04/2009 12:26, "jon.hart" <jon.hart@web.de> wrote:

> If a domU crash happens all I can do is to destroy this guest because it
> is unaccessable in this state.
> 
> My questions are: is there an other kernel tree I can try? What can I do
> to figure out what the problem is or to fix this?

You could try http://xenbits.xensource.com/linux-2.6.18-xen.hg in a domU and
see if that stabilises that particular domU. The bug looks possibly like a
spinlock deadlock within the domU kernel, or possibly a bug in the
paravirtualised spinlock implementation.

 -- Keir