All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eduardo Habkost <ehabkost@redhat.com>
To: Marcel Apfelbaum <marcel@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Kevin Wolf <kwolf@redhat.com>, Gerd Hoffmann <kraxel@redhat.com>,
	"Tian, Kevin" <kevin.tian@intel.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	libvir-list@redhat.com, Thomas Huth <thuth@redhat.com>,
	qemu-devel@nongnu.org, Chao Peng <chao.p.peng@linux.intel.com>,
	Laszlo Ersek <lersek@redhat.com>
Subject: Re: [Qemu-devel] change x86 default machine type to Q35?
Date: Wed, 12 Jul 2017 12:17:52 -0300	[thread overview]
Message-ID: <20170712151752.GG6020@localhost.localdomain> (raw)
In-Reply-To: <8d6ed662-63e5-fe49-f41e-05f80a52bc20@redhat.com>

On Wed, Jul 12, 2017 at 09:39:39AM +0300, Marcel Apfelbaum wrote:
> On 11/07/2017 17:47, Paolo Bonzini wrote:
> > On 11/07/2017 16:42, Kevin Wolf wrote:
> > > > >   Concerning QEMU, could we maybe simply emit a warning a la
> > > > > 
> > > > >   "you did not specify a machine type with the -M option, so you are
> > > > >    currently running the the 'pc' machine type. Please note that
> > > > > future
> > > > >    versions of QEMU might use the 'q35' machine type instead. If you
> > > > >    require the 'pc' machine type for your setting, then please specify
> > > > >    it with the -M option."
> > > > Warnings tend to get ignored until things are actually break, so I
> > > > don't think this helps much.  I think simply not having a default
> > > > machine type (as already suggested elsewhere in this thread) is the
> > > > best way to deal with this.
> > > I would absolutely hate this. One of the nice things about qemu has
> > > always been that 'qemu disk.img' is enough to start a simple VM. You
> > > only need to touch any other options for things you care about. I
> > > wouldn't want to give this up.
> > 
> > I agree.  Don't change anything, leave "-M pc" aside, and let libosinfo
> > pick q35 for newer guests.
> > 
> 
> Hi Paolo,
> 
> While I do think it would be a good step moving forward, I am not
> convinced is "enough" to get more users using it. More so, a low
> level bug in upper layers (e.g. Open stack) will lead to difficulty
> to debug and result in the same "The machine is not steady enough,
> it doesn't worth the effort, let's move back to pc", or even
> frustration of the people that really need Q35.

I guess not being enough depends on which users we want to
affect.  People who run QEMU from the command-line don't get a
virtio drive or a modern CPU model chosen by default, either.  Is
the choice of machine-type different?  Why?

> [...]

-- 
Eduardo

  reply	other threads:[~2017-07-12 15:18 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-05  6:57 [Qemu-devel] change x86 default machine type to Q35? Chao Peng
2017-07-05  8:14 ` Thomas Huth
2017-07-05  9:32   ` Marcel Apfelbaum
2017-07-07 13:39     ` Eduardo Habkost
2017-07-07 15:17       ` Michael S. Tsirkin
2017-07-07 18:03         ` Eduardo Habkost
2017-07-10  7:42           ` Marcel Apfelbaum
2017-07-10  9:45             ` Paolo Bonzini
2017-07-10 13:59             ` Eduardo Habkost
2017-07-10 16:45               ` Michael S. Tsirkin
2017-07-10 17:47                 ` Eduardo Habkost
2017-07-11  7:48                   ` Thomas Huth
2017-07-11  8:01                     ` Marcel Apfelbaum
2017-07-11  8:13                     ` Gerd Hoffmann
2017-07-11 14:42                       ` Kevin Wolf
2017-07-11 14:47                         ` Paolo Bonzini
2017-07-12  6:39                           ` Marcel Apfelbaum
2017-07-12 15:17                             ` Eduardo Habkost [this message]
2017-07-12  5:51                         ` Gerd Hoffmann
2017-07-12  6:18                           ` Marcel Apfelbaum
2017-07-12  8:28                           ` Kevin Wolf
2017-07-11 14:47                       ` Eduardo Habkost
2017-07-05 11:07   ` Daniel P. Berrange
2017-07-05 11:13     ` Thomas Huth
2017-07-06 10:30     ` Stefan Hajnoczi
2017-07-06 10:41       ` Daniel P. Berrange
2017-07-11 10:13         ` Stefan Hajnoczi
2017-07-05 10:49 ` Laszlo Ersek
2017-07-05 11:04 ` Daniel P. Berrange
2017-07-05 11:44   ` Fam Zheng
2017-07-05 11:58     ` Thomas Huth
2017-07-05 12:22       ` Fam Zheng
2017-07-06 10:49         ` Daniel P. Berrange
2017-07-06 10:57           ` Peter Maydell
2017-07-06 11:00           ` Thomas Huth
2017-07-06 11:06             ` Daniel P. Berrange
2017-07-06 11:12               ` Thomas Huth
2017-07-06 11:13               ` Dr. David Alan Gilbert
2017-07-07 13:49           ` Eduardo Habkost
2017-07-05 12:43       ` Paolo Bonzini

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=20170712151752.GG6020@localhost.localdomain \
    --to=ehabkost@redhat.com \
    --cc=chao.p.peng@linux.intel.com \
    --cc=kevin.tian@intel.com \
    --cc=kraxel@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=lersek@redhat.com \
    --cc=libvir-list@redhat.com \
    --cc=marcel@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.