qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	Markus Armbruster <armbru@redhat.com>,
	zhang.zhanghailiang@huawei.com,
	Ben Warren <ben@skyportsystems.com>,
	qemu-trivial@nongnu.org, qemu-devel@nongnu.org,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [RFC PATCH 4/4] qemu-options: Do not show -enable-kvm and -enable-hax in the docs anymore
Date: Tue, 26 Jun 2018 09:50:04 +0200	[thread overview]
Message-ID: <20180626095004.7e92fdaa.cohuck@redhat.com> (raw)
In-Reply-To: <54dfe708-cccf-c628-753f-692c83391ec4@redhat.com>

On Tue, 26 Jun 2018 06:40:56 +0200
Thomas Huth <thuth@redhat.com> wrote:

> On 25.06.2018 20:26, Paolo Bonzini wrote:
> > On 25/06/2018 19:30, Eduardo Habkost wrote:  
> >>>> Attentive distros could even replace the wrapper script by a link.  
> >>> If they are okay with replacing the "KVM only" semantics with "KVM or
> >>> TCG", which I think is generally worse.  
> >>
> >> If we can't get agreement on what's the right default for each
> >> QEMU binary, I think that's yet another reason to document that
> >> upstream QEMU won't guarantee ABI compatibility if -accel is
> >> omitted.  
> > 
> > Before that we should ask what the benefit is in changing the default
> > for qemu-system-*.  Nobody is using it in practice to start QEMU with
> > KVM enabled...  
> 
> That's certainly not true. I've seen a couple of times already that
> people ask on IRC why their guests are running so slow, and if you ask
> them about their command line, it's obvious that they simply were not
> aware of "-accel" / "-enable-kvm" yet.
> 
> <semi-sarcastic>
> Maybe we simply should add a "--verbose" command line option that people
> can use to diagnose their problems:
> 
> $ qemu-system-x86_64 --verbose
> QEMU emulator version 2.12.50
> Using 'tcg' accelerator. Use '-accel kvm' to speed things up.
> Machine type is 'pc-i440fx-3.0'. Use 'q35' for a more modern machine.
> ....
> </semi-sarcastic>

Not sure how serious you meant that, but I actually quite like the
idea :)

  reply	other threads:[~2018-06-26  7:50 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-13  5:05 [Qemu-devel] [PATCH 0/4] Clean up accelerator options Thomas Huth
2018-06-13  5:05 ` [Qemu-devel] [PATCH 1/4] Replace '-machine accel=xyz' with '-accel xyz' Thomas Huth
2018-06-13 12:20   ` Eric Blake
2018-06-13 12:48   ` Paolo Bonzini
2018-06-13 12:53     ` Thomas Huth
2018-06-13 13:54       ` Paolo Bonzini
2018-06-13 14:12         ` Thomas Huth
2018-06-13 16:10       ` Eduardo Habkost
2018-06-13 13:38   ` Stefan Hajnoczi
2018-06-13  5:05 ` [Qemu-devel] [PATCH 2/4] Replace '-enable-kvm' with '-accel kvm' in docs and help texts Thomas Huth
2018-06-13 12:51   ` Paolo Bonzini
2018-06-13 13:38   ` Stefan Hajnoczi
2018-06-13  5:05 ` [Qemu-devel] [PATCH 3/4] qemu-options: Improve the documentation of '-accel' and '-machine accel=...' Thomas Huth
2018-06-13 13:38   ` Stefan Hajnoczi
2018-06-13  5:05 ` [Qemu-devel] [RFC PATCH 4/4] qemu-options: Do not show -enable-kvm and -enable-hax in the docs anymore Thomas Huth
2018-06-13 12:51   ` Paolo Bonzini
2018-06-13 13:38   ` Stefan Hajnoczi
2018-06-13 13:44     ` Daniel P. Berrangé
2018-06-13 15:11       ` Thomas Huth
2018-06-13 15:19         ` Daniel P. Berrangé
2018-06-13 15:44           ` Thomas Huth
2018-06-13 16:02           ` Markus Armbruster
2018-06-19 15:15             ` Cornelia Huck
2018-06-19 16:16               ` Paolo Bonzini
2018-06-22 18:11                 ` Eduardo Habkost
2018-06-22 19:19                   ` Thomas Huth
2018-06-22 19:35                     ` Eduardo Habkost
2018-06-22 21:22                       ` Paolo Bonzini
2018-06-25  6:50                         ` Markus Armbruster
2018-06-25 10:28                           ` Paolo Bonzini
2018-06-25 17:30                             ` Eduardo Habkost
2018-06-25 18:26                               ` Paolo Bonzini
2018-06-25 19:51                                 ` Eduardo Habkost
2018-06-26  5:57                                   ` Paolo Bonzini
2018-06-26 12:29                                     ` Eduardo Habkost
2018-06-26 13:05                                       ` Paolo Bonzini
2018-06-26 16:06                                         ` Eduardo Habkost
2018-06-26 16:10                                           ` Daniel P. Berrangé
2018-06-27  8:39                                           ` Paolo Bonzini
2018-06-27 14:05                                             ` Eduardo Habkost
2018-06-26  4:40                                 ` Thomas Huth
2018-06-26  7:50                                   ` Cornelia Huck [this message]
2018-06-26 12:56                                     ` Eduardo Habkost
2018-06-26 16:43                                       ` Markus Armbruster
2018-06-27  8:49                                         ` Paolo Bonzini
2018-06-13 13:39 ` [Qemu-devel] [PATCH 0/4] Clean up accelerator options Stefan Hajnoczi

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=20180626095004.7e92fdaa.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=armbru@redhat.com \
    --cc=ben@skyportsystems.com \
    --cc=ehabkost@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=thuth@redhat.com \
    --cc=zhang.zhanghailiang@huawei.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;
as well as URLs for NNTP newsgroup(s).