From: Glauber Costa <glommer@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Alexander Graf <agraf@suse.de>, Avi Kivity <avi@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH] exit if we fail to initialize kvm
Date: Wed, 29 Jul 2009 12:50:44 -0300 [thread overview]
Message-ID: <20090729155044.GE4776@poweredge.glommer> (raw)
In-Reply-To: <4A705FFF.5060503@siemens.com>
On Wed, Jul 29, 2009 at 04:43:11PM +0200, Jan Kiszka wrote:
> Alexander Graf wrote:
> > Avi Kivity wrote:
> >> On 07/29/2009 01:17 PM, Jan Kiszka wrote:
> >>> I just wonder now if/when qemu-kvm will switch over to the
> >>> kvm-by-default-off policy of upstream?
> >>>
> >> That will surely inconvenience/surprise a lot of users.
> >>
> >> A migration path could be:
> >>
> >> - add -accel
> >> - start warning when -accel is not used, encouraging people to use -accel
> >> - time passes
> >> - switch default to tcg (maybe unless invoked with kvm in argv[0])
> >> - time passes
> >> - remove warning
> >>
> >
> > I would prefer:
> >
> > - add -accel (default to kvm)
> > - give a message to use -accel tcg when the user wants tcg
> > - make -accel go kvm,kqemu,tcg in qemu upstream
>
> Upstream just dropped the behavior '-accel kqemu,tcg', so I'm not sure
> if this is desired to return (though I'm surely not comparing kvm to
> kqemu here).
>
> > - have distros / management tools decide which accel they like
>
> That's likely the key: explicit -accel.
While I do understand the value of backwards compatibility, we did change
behaviour of a number of things in the past. Example: "qemu" would print a help message,
and now it runs without any disks. It changed people's script already.
It should probably be okay to drop all kvm,kqemu,whatever-related options in favour
of accel if we are doing this in a release boundary.
next prev parent reply other threads:[~2009-07-29 15:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-28 20:52 [PATCH] exit if we fail to initialize kvm Glauber Costa
2009-07-28 21:12 ` Alexander Graf
2009-07-28 21:15 ` Alexander Graf
2009-07-28 21:28 ` Glauber Costa
2009-07-28 21:38 ` Alexander Graf
2009-07-28 22:12 ` Alexander Graf
2009-07-29 10:17 ` Jan Kiszka
2009-07-29 11:49 ` Avi Kivity
2009-07-29 12:28 ` Alexander Graf
2009-07-29 12:47 ` Avi Kivity
2009-07-29 14:43 ` Jan Kiszka
2009-07-29 15:50 ` Glauber Costa [this message]
2009-07-29 15:52 ` 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=20090729155044.GE4776@poweredge.glommer \
--to=glommer@redhat.com \
--cc=agraf@suse.de \
--cc=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.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