From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: trying to debug xen4 & qemu-dm, Xen reports "core
	dump failed"
Date: Tue, 26 Jan 2010 13:36:04 -0500
Message-ID: <20100126183604.GB14410@phenom.dumpdata.com>
References: <c67eed301001261036t6403fe71qa9040ab39242eb8c@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
In-Reply-To: <c67eed301001261036t6403fe71qa9040ab39242eb8c@mail.gmail.com>
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: 0bo0 <0.bugs.only.0@gmail.com>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

> speculation of what may be the case isn't helping _me_ find the
> problem, so i'll try to debug this a step at a time.  any suggestions
> as to *specific* steps to take in debugging this would be great.
> here's all the info i can muster atm ...

You are missing this one:

[2010-01-26 10:09:10 4764] WARNING (image:561) domain test: device                                                                  
model failure: pid 5379: malfunctioning (closed sentinel), killed; see                                                              
/var/log/xen/qemu-dm-test.log        

Can you see what it has?