All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Lieven <pl@dlh.net>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: Live Migration of 32-bit Linux guest broken since	2.6.35-rc2
Date: Tue, 08 Jun 2010 14:59:12 +0200	[thread overview]
Message-ID: <4C0E3EA0.6080909@dlh.net> (raw)
In-Reply-To: <4C0E3CD5.4070202@redhat.com>

Avi Kivity wrote:
> 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).
mhh, i am at the moment back to 2.6.34. here i do not see the nx flag in 
the guest
of both 32-bit and 64-bit linux.
>
>> 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.
>


-- 
Mit freundlichen Grüßen/Kind Regards

Peter Lieven

..........................................................................................................

   KAMP Netzwerkdienste GmbH
   Vestische Str. 89-91 | 46117 Oberhausen
   Tel: +49 (0) 208.89 402-50 | Fax: +49 (0) 208.89 402-40
   mailto:pl@kamp.de | http://www.kamp.de

   Geschäftsführer: Heiner Lante | Michael Lante
   Amtsgericht Duisburg | HRB Nr. 12154
   USt-Id-Nr.: DE 120607556

......................................................................................................... 


WARNING: multiple messages have this Message-ID (diff)
From: Peter Lieven <pl@dlh.net>
To: Avi Kivity <avi@redhat.com>
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 14:59:12 +0200	[thread overview]
Message-ID: <4C0E3EA0.6080909@dlh.net> (raw)
In-Reply-To: <4C0E3CD5.4070202@redhat.com>

Avi Kivity wrote:
> 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).
mhh, i am at the moment back to 2.6.34. here i do not see the nx flag in 
the guest
of both 32-bit and 64-bit linux.
>
>> 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.
>


-- 
Mit freundlichen Grüßen/Kind Regards

Peter Lieven

..........................................................................................................

   KAMP Netzwerkdienste GmbH
   Vestische Str. 89-91 | 46117 Oberhausen
   Tel: +49 (0) 208.89 402-50 | Fax: +49 (0) 208.89 402-40
   mailto:pl@kamp.de | http://www.kamp.de

   Geschäftsführer: Heiner Lante | Michael Lante
   Amtsgericht Duisburg | HRB Nr. 12154
   USt-Id-Nr.: DE 120607556

......................................................................................................... 

  reply	other threads:[~2010-06-08 12:59 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-07 21:03 Live Migration of 32-bit Linux guest broken since 2.6.32-rc2 Peter Lieven
2010-06-07 21:03 ` [Qemu-devel] " Peter Lieven
2010-06-08  9:13 ` Live Migration of 32-bit Linux guest broken since 2.6.35-rc2 Peter Lieven
2010-06-08  9:13   ` [Qemu-devel] " Peter Lieven
2010-06-08 11:29   ` Avi Kivity
2010-06-08 11:29     ` [Qemu-devel] " Avi Kivity
2010-06-08 11:31     ` Avi Kivity
2010-06-08 11:31       ` [Qemu-devel] " Avi Kivity
2010-06-08 11:51       ` Avi Kivity
2010-06-08 11:51         ` [Qemu-devel] " Avi Kivity
2010-06-08 12:49         ` Peter Lieven
2010-06-08 12:49           ` [Qemu-devel] " Peter Lieven
2010-06-08 12:51           ` Avi Kivity
2010-06-08 12:51             ` [Qemu-devel] " Avi Kivity
2010-06-08 12:59             ` Peter Lieven [this message]
2010-06-08 12:59               ` Peter Lieven
2010-06-08 13:28             ` Peter Lieven
2010-06-08 13:28               ` [Qemu-devel] " Peter Lieven
2010-06-08 13:34               ` Avi Kivity
2010-06-08 13:34                 ` [Qemu-devel] " Avi Kivity
2010-06-08 13:38                 ` Peter Lieven
2010-06-08 13:38                   ` [Qemu-devel] " Peter Lieven
2010-06-08 13:40                   ` Avi Kivity
2010-06-08 13:40                     ` [Qemu-devel] " Avi Kivity
2010-06-08 13:44                     ` Peter Lieven
2010-06-08 13:44                       ` [Qemu-devel] " Peter Lieven
2010-06-08 13:45                       ` Avi Kivity
2010-06-08 13:45                         ` [Qemu-devel] " Avi Kivity
2010-06-09  8:29                         ` Peter Lieven
2010-06-09  8:29                           ` [Qemu-devel] " Peter Lieven
2010-06-09 15:08                           ` Avi Kivity
2010-06-09 15:08                             ` [Qemu-devel] " Avi Kivity
2010-06-09 15:12                             ` Gleb Natapov
2010-06-09 15:12                               ` [Qemu-devel] " Gleb Natapov
2010-06-09 15:17                               ` Avi Kivity
2010-06-09 15:17                                 ` [Qemu-devel] " 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=4C0E3EA0.6080909@dlh.net \
    --to=pl@dlh.net \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --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 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.