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: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Date: Thu, 27 Jan 2011 20:57:32 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Delivery-date: Thu, 27 Jan 2011 12:59:01 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4D41D8B6.9020407@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>
Organization: Citrix Systems, Inc.
References: <4D41D3BA.7090602@xxxxxx> <20110127203609.GC4194@xxxxxxxxxxxx> <4D41D8B6.9020407@xxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, 2011-01-27 at 20:42 +0000, Nathan March wrote: 
> On 1/27/2011 12:36 PM, Konrad Rzeszutek Wilk wrote:
> > Whoa.. nice job figuring out what is wrong. One question: did you
> > try to use the git branch from Jeremy's tree as a DomU?
> >
> No, should I? I've been under the impression that domU support in 
> mainline has been pretty solid for a while now. I'll give it a try if 
> you think it's worth it.

I think it's worth a shot since it would indicate whether or not we have
simply missed getting a patch into the upstream stable kernel or if we
have a totally new issue.

I fixed a bunch of migration issues which were introduced in the time frame around about the time frame (IIRC my
memory's a bit fuzzy). I wasn't aware of any further subsequent breakage

Are the guests 32 or 64 bit? How about the hypervisor and dom0 kernel?
What is your kernel's .config?

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.

> > git bisect is a great tool for this. You can fetch Linus's tree and
> > the tools for this - takes only about a day to find the culprit.
> >
> Haven't worked with git much yet but I'll take a look!

Thanks, that would be worthwhile.


Xen-devel mailing list