public inbox for kvm@vger.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 15:44:15 +0200	[thread overview]
Message-ID: <4C0E492F.6060203@dlh.net> (raw)
In-Reply-To: <4C0E484D.4060609@redhat.com>

Avi Kivity wrote:
> On 06/08/2010 04:38 PM, Peter Lieven wrote:
>> Avi Kivity wrote:
>>> On 06/08/2010 04:28 PM, Peter Lieven wrote:
>>>>>
>>>>>> 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).
>>>>
>>>> do you have a guideline which flags should be identical to ensure 
>>>> proper live migration?
>>>> i would like to do an automatic compare before life migration to 
>>>> avoid crashes.
>>>
>>> All of them [1].  If you have an asymmetric machine, you can disable 
>>> those flags with the -cpu switch.
>>>
>>> Note the default qemu cpu disables many flags, so if one machine has 
>>> sse4.2 and the other doesn't, migration will still work without 
>>> disabling anything.
>> which cpu model do you suggest for 4 core xeon cpus? -cpu host ?
>
> -cpu host is good if you have identical machines and don't plan to add 
> new ones.
i will likely add new ones, but my plan would be to use qemu64 and then 
add all flags manually that
are common to all cpus in the pool.
would that be safe?

br,
peter

>
>> how important is the match of the virtualization extensions?
>
> The virtualization extensions on Intel aren't exposed to the guest, so 
> they don't need to match.
>


-- 
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 13:44 UTC|newest]

Thread overview: 19+ 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-08  9:13 ` Live Migration of 32-bit Linux guest broken since 2.6.35-rc2 Peter Lieven
2010-06-08 11:29   ` 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
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 [this message]
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     ` [Qemu-devel] " 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=4C0E492F.6060203@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox