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] Live migration bug introduced in

To: Nathan March <nathan@xxxxxx>
Subject: Re: [Xen-devel] Live migration bug introduced in
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Thu, 27 Jan 2011 18:27:30 -0500
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Delivery-date: Thu, 27 Jan 2011 15:29:00 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4D41F7BE.3050809@xxxxxx>
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: <4D41D3BA.7090602@xxxxxx> <20110127203609.GC4194@xxxxxxxxxxxx> <4D41D8B6.9020407@xxxxxx> <1296161852.20804.55.camel@xxxxxxxxxxxxxxxxxxxxx> <4D41F7BE.3050809@xxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.20 (2009-06-14)
On Thu, Jan 27, 2011 at 02:54:54PM -0800, Nathan March wrote:
> On 1/27/2011 12:57 PM, Ian Campbell wrote:
> >
> >Are the guests 32 or 64 bit? How about the hypervisor and dom0 kernel?
> >What is your kernel's .config?
> All 64bit. Config is attached.
> >If you edit /etc/sysconfig/{xencommons,xend} (whichever one you have)
> >then you can set XENCONSOLED_TRACE=guest which will write guest consoles
> >to /var/log/xen/domain. Also setting "on_crash=preserve" in your guest
> >configuration will hopefully cause them to stick around long enough to
> >see what was on the console.
> >
> Will try that. The domUs don't actually fully crash, they just lock
> up. The VM keeps running until I destroy it. Trying to attach to the
> console when it's in this state results in xenconsole hanging on an
> select against fd 3/4/5 (socket, pipe + pipe)

You could run 'xenctx' and get a stack trace of what the guest is doing.
That could narrow it down.

> I'll try all the things suggested and let you guys know what I find.


Xen-devel mailing list