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

To: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Subject: Re: [Xen-devel] Live migration bug introduced in 2.6.32.16?
From: Nathan March <nathan@xxxxxx>
Date: Thu, 27 Jan 2011 14:54:54 -0800
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Delivery-date: Thu, 27 Jan 2011 14:56:16 -0800
Dkim-signature: v=1; a=rsa-sha1; c=relaxed; d=gt.net; h=message-id:date :from:mime-version:to:cc:subject:references:in-reply-to :content-type; s=mail; bh=an+I2dxTefzQ7/UGdT/2lPVPBrM=; b=FEpMzJ yo6t22TZTRwJL2jiZvE6FmKk1vJOpSPBJnXgXYma+yQOXU6wCf7f29py/VA6j1fm z32CIhFEuBY5b+R4ztQFuLRO9od6N1GS4ogcrPyGWIK1llZ9Yzg+sVxnKZLImAjB zxlUIamRE/V5sTKJa8lFdw1SfPYSShCht5UD0=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gt.net; h=message-id:date :from:mime-version:to:cc:subject:references:in-reply-to :content-type; q=dns; s=mail; b=QL82FQc2TWy4kI2ZoIDjRX+SbXLu/g8R ym5T5IdODkCpB0P7fqDA71UUf4JcgtJBHdPI4qPUdcRDy9CtKV4rplMJ0RZq0da4 pZkRizkHAqkR0qH7M1soUMRzSK/A2zksz5RAciba4dxkx4bXXcK6mJNXUS4MGYJX Ro5PIlS87Ao=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1296161852.20804.55.camel@xxxxxxxxxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
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)

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

- Nathan

Attachment: .config
Description: Text document

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