All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Marcel Apfelbaum <marcel@redhat.com>,
	Thomas Huth <thuth@redhat.com>,
	Chao Peng <chao.p.peng@linux.intel.com>,
	qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
	"Tian, Kevin" <kevin.tian@intel.com>,
	Laszlo Ersek <lersek@redhat.com>
Subject: Re: [Qemu-devel] change x86 default machine type to Q35?
Date: Fri, 7 Jul 2017 18:17:57 +0300	[thread overview]
Message-ID: <20170707181642-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20170707133949.GH10776@localhost.localdomain>

On Fri, Jul 07, 2017 at 10:39:49AM -0300, Eduardo Habkost wrote:
> On Wed, Jul 05, 2017 at 12:32:10PM +0300, Marcel Apfelbaum wrote:
> > On 05/07/2017 11:14, Thomas Huth wrote:
> > >   Hi,
> > > 
> > 
> > Hi,
> > 
> > > On 05.07.2017 08:57, Chao Peng wrote:
> > > > 
> > > > Q35 has been in QEMU for quite a while. Compared to the current default
> > > > i440FX, Q35 is probably not that mature and not widely used, however in
> > > > some case, Q35 has advantages, for example, in supporting new features.
> > > > For instance, we have some features require PCI-e support which is only
> > > > available on Q35 and some others need it for EFI support. It is of
> > > > course not necessary to change it as the default but if more and more
> > > > features have dependencies on Q35 because of requiring much more modern
> > > > features then I think it may be worth to do so. In such case we can have
> > > > more people to use it and find problems we may know or not know.
> > > 
> > 
> > Agreed
> > 
> > > Yes, IMHO at one point in time, we should switch the default machine
> > > type to q35.
> > 
> > +1
> > 
> > > The i440FX is really quite old...
> > > 
> > > > There are certainly some drawbacks:
> > > > -        Compatibility: current code or script may need adjustment
> > > 
> > > That might be a real concern ...
> > 
> > I am not so sure about that. Developers working on upstream projects
> > should expect such changes and, for our case,
> > modifying the command line by adding "-M pc" should not be a big deal.
> 
> We could print a warning for 1 or 2 releases when users don't add
> a explicit "-M pc" or "-M q35" argument to qemu-system-x86_64,
> but:
> 
> > 
> > The upper layers should manage the defaults by themselves so
> > are not supposed to be affected.
> 
> But they would be.  libvirt uses the default machine-type from
> QEMU.

How about extending the command for supported machines with a
recommended machine type, and teaching libvirt to use that?

This way no existing users will be affected.

> 
> > [...]
> 
> -- 
> Eduardo

  reply	other threads:[~2017-07-07 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 [this message]
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
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=20170707181642-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=chao.p.peng@linux.intel.com \
    --cc=ehabkost@redhat.com \
    --cc=kevin.tian@intel.com \
    --cc=lersek@redhat.com \
    --cc=marcel@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.