From: Avi Kivity <avi@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: kvm@vger.kernel.org, "Daniel P. Berrange" <berrange@redhat.com>,
"Richard W. M. Jones" <rjones@redhat.com>,
Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [PATCH v2] qemu-kvm: Switch to upstream -enable-kvm semantics
Date: Thu, 30 Dec 2010 12:21:18 +0200 [thread overview]
Message-ID: <4D1C5D1E.6030309@redhat.com> (raw)
In-Reply-To: <m3vd2m7zrw.fsf@blackfin.pond.sub.org>
On 12/22/2010 02:33 PM, Markus Armbruster wrote:
> We currently enable KVM by default, and when it's not available, we
> print a message and fall back to TCG. Option -enable-kvm is ignored.
> Option -no-kvm suppresses KVM.
>
> Upstream works differently: KVM is off by default, -enable-kvm
> switches it on. -enable-kvm terminates the process unsuccessfully if
> KVM is not available.
>
> upstream qemu | default |-enable-kvm
> ----------------+-----------+-----------
> KVM available | disabled | enabled
> KVM unavailable | disabled | fail
>
> qemu-kvm | default |-enable-kvm| -no-kvm
> ----------------+-----------+-----------+----------
> KVM available | enabled* | enabled | disabled
> KVM unavailable | disabled | disabled* | disabled
>
> * differs from upstream
>
> Users of qemu and qemu-kvm need to be aware of these differences to
> enable / disable use of KVM reliably. This is bothersome.
>
> Consider -enable-kvm when KVM is unavailable: If the user expects
> qemu-kvm behavior (fall back), but qemu fails, he'll likely be
> surprised and unhappy. If the user expects upstream behavior (fail),
> but qemu-kvm falls back to TCG, the guest runs slow as molasses, and
> the user will likely be confused and unhappy (unless he spots and
> understands the "disable KVM" message).
>
> Eventually, we'll sort this upstream with -accel (defaults tied to
> machine type). Until then, this patch reduces the difference to
> upstream so that most users shouldn't need to be aware of them.
>
> Make -enable-kvm behave just like in upstream: enable KVM, fail if not
> available. But retain current default behavior: enable KVM, fall back
> to TCG.
>
> qemu-kvm new | default |-enable-kvm| -no-kvm
> ----------------+-----------+-----------+-----------
> KVM available | enabled* | enabled | disabled
> KVM unavailable | disabled | fail+ | disabled
>
> * differs from upstream
> + changed by this patch
>
> Bonus fix: -no-kvm -enable-kvm now enables KVM. Before, it disabled it.
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-12-30 10:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-22 12:33 [PATCH v2] qemu-kvm: Switch to upstream -enable-kvm semantics Markus Armbruster
2010-12-30 10:21 ` Avi Kivity [this message]
2011-01-02 10:15 ` Jan Kiszka
2011-01-02 10:18 ` Avi Kivity
2011-01-02 18:27 ` David Mair
2011-01-03 0:06 ` Alexander Graf
2011-01-02 19:52 ` Richard W.M. Jones
2011-01-03 8:28 ` Avi Kivity
2011-01-03 11:18 ` Richard W.M. Jones
2011-01-03 11:40 ` Avi Kivity
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=4D1C5D1E.6030309@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=rjones@redhat.com \
/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