[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] Live migration bug introduced in 2.6.32.16?
- To: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
- 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
- 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=
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
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
|
