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: Wed, 09 Jun 2010 10:29:33 +0200 [thread overview]
Message-ID: <4C0F50ED.7060109@dlh.net> (raw)
In-Reply-To: <4C0E495C.8020008@redhat.com>
Avi Kivity wrote:
> On 06/08/2010 04:44 PM, Peter Lieven wrote:
>>> -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?
>
> Yes.
>
2 last questions:
a) i remember that there (have been) are instructions that have a high
virtualization penalty.
are there flags that should better not be offered to a VM?
b) you told you fixed another bug in 2.6.35. is the nx virtualization
not working in guests
before 2.6.35 and therefore my case worked with 2.6.34?
thanks
peter
next prev parent reply other threads:[~2010-06-09 8:30 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
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 [this message]
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=4C0F50ED.7060109@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;
as well as URLs for NNTP newsgroup(s).