Re: [Xen-devel] Live migration bug introduced in 2.6.32.16?

[Pasi Kärkkäinen <pasik@xxxxxx>]

On Thu, Jan 27, 2011 at 06:27:30PM -0500, Konrad Rzeszutek Wilk wrote:
> 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.
> 

xenctx usage is described here:
http://wiki.xen.org/xenwiki/XenCommonProblems#head-61843b32f0243b5ad0e17850f9493bffd80f8c17

-- Pasi

> > 
> > I'll try all the things suggested and let you guys know what I find.
> 
> OK.
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

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