From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Nathan March <nathan@gt.net>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: Live migration bug introduced in 2.6.32.16?
Date: Thu, 27 Jan 2011 18:27:30 -0500 [thread overview]
Message-ID: <20110127232730.GA8749@dumpdata.com> (raw)
In-Reply-To: <4D41F7BE.3050809@gt.net>
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.
OK.
next prev parent reply other threads:[~2011-01-27 23:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 20:21 Live migration bug introduced in 2.6.32.16? Nathan March
2011-01-27 20:36 ` Konrad Rzeszutek Wilk
2011-01-27 20:42 ` Nathan March
2011-01-27 20:57 ` Ian Campbell
2011-01-27 22:54 ` Nathan March
2011-01-27 23:27 ` Konrad Rzeszutek Wilk [this message]
2011-01-28 8:53 ` Pasi Kärkkäinen
2011-01-28 0:51 ` Nathan March
2011-01-28 6:47 ` Philipp Hahn
2011-01-28 8:44 ` Ian Campbell
2011-01-28 18:44 ` Nathan March
2011-02-04 14:17 ` Ian Campbell
2011-02-04 14:46 ` [Xen-devel] " Greg KH
2011-02-04 14:51 ` Ian Campbell
2011-02-16 21:47 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110127232730.GA8749@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=nathan@gt.net \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.