From: Avi Kivity <avi@redhat.com>
To: Peter Lieven <pl@dlh.net>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: Live Migration of 32-bit Linux guest broken since 2.6.35-rc2
Date: Tue, 08 Jun 2010 15:51:33 +0300 [thread overview]
Message-ID: <4C0E3CD5.4070202@redhat.com> (raw)
In-Reply-To: <4C0E3C46.30901@dlh.net>
On 06/08/2010 03:49 PM, Peter Lieven wrote:
>>
>> And finally, perhaps you have NX disabled in the bios of one of the
>> machines?
>>
>> What does 'dmesg | grep NX' show on both hosts?
>>
>
> nx was disabled on one of the nodes.
That explains the problem.
> i will retry the case later today and send info register output.
> what is the recommended value for nx (and why)?
Enabled (so you get no-execute memory protection).
> and why was it working with 2.6.34 and is not with 2.6.35-rc2?
We fixed a different bug. But you shouldn't live migrate from a machine
with nx to a machine without nx, unless you use -cpu ...,-nx on both nodes.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-06-08 12:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-07 21:03 [Qemu-devel] Live Migration of 32-bit Linux guest broken since 2.6.32-rc2 Peter Lieven
2010-06-08 9:13 ` [Qemu-devel] Live Migration of 32-bit Linux guest broken since 2.6.35-rc2 Peter Lieven
2010-06-08 11:29 ` [Qemu-devel] " Avi Kivity
2010-06-08 11:31 ` Avi Kivity
2010-06-08 11:51 ` Avi Kivity
2010-06-08 12:49 ` Peter Lieven
2010-06-08 12:51 ` Avi Kivity [this message]
2010-06-08 12:59 ` Peter Lieven
2010-06-08 13:28 ` Peter Lieven
2010-06-08 13:34 ` Avi Kivity
2010-06-08 13:38 ` Peter Lieven
2010-06-08 13:40 ` Avi Kivity
2010-06-08 13:44 ` Peter Lieven
2010-06-08 13:45 ` Avi Kivity
2010-06-09 8:29 ` Peter Lieven
2010-06-09 15:08 ` Avi Kivity
2010-06-09 15:12 ` Gleb Natapov
2010-06-09 15:17 ` Avi Kivity
2010-06-08 11:38 ` Peter Lieven
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=4C0E3CD5.4070202@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pl@dlh.net \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).