qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>
Cc: eduardo@habkost.net, libvir-list@redhat.com, thuth@redhat.com,
	qemu-devel@nongnu.org, kraxel@redhat.com
Subject: Re: [PATCH] deprecation: x86 default machine types
Date: Wed, 2 Mar 2022 17:42:05 +0000	[thread overview]
Message-ID: <Yh+sbYC5n4DsZWWg@redhat.com> (raw)
In-Reply-To: <20220301195432.114252-1-dgilbert@redhat.com>

On Tue, Mar 01, 2022 at 07:54:32PM +0000, Dr. David Alan Gilbert (git) wrote:
> From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
> 
> Declare the intent to require a machine type to be specified on x86
> system emulation.
> 
> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> ---
>  docs/about/deprecated.rst | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/docs/about/deprecated.rst b/docs/about/deprecated.rst
> index 85773db631..143c60d105 100644
> --- a/docs/about/deprecated.rst
> +++ b/docs/about/deprecated.rst
> @@ -324,6 +324,14 @@ machine is hardly emulated at all (e.g. neither the LCD nor the USB part had
>  been implemented), so there is not much value added by this board. Use the
>  ``ref405ep`` machine instead.
>  
> +x86 default machine type
> +''''''''''''''''''''''''
> +
> +x86 currently defaults to the ```pc``` machine type which is based on the very
> +old ```i440fx``` chipset.  This default will be removed and the user will be
> +required to specify a machine type explicitly using -M; users are encouraged to
> +switch to the not quite as old ```q35``` machine types.

This will have no impact on anyone using libvirt as a mgmt app,
because it will explicitly set 'pc' if the user doesn't request
a machine type.

It will, however, break a huge number of users who don't use
libvirt or a similar mgmt app.

'q35' is not a drop in replacement for 'pc', and even though
it is slightly newer, the features it brings are not likely
to be important enough for most users who aren't using a mgmt
app to care about switching.

In the ongoing work to introduce a completely new system
emulator binary that is exclusively runtime QMP configured,
the machine type will almost certainly be mandatory, without
affecting existing users. That would also apply consistently
across all target arches.

Overall I'm just not seeing enough benefit to justify the
disruption we'll cause by making this change to existing
system emulator binaries.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2022-03-02 17:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01 19:54 [PATCH] deprecation: x86 default machine types Dr. David Alan Gilbert (git)
2022-03-02 17:42 ` Daniel P. Berrangé [this message]
2022-03-02 19:38   ` Dr. David Alan Gilbert
2022-03-03  8:59     ` Daniel P. Berrangé
2022-03-03 18:59       ` Dr. David Alan Gilbert
2022-03-02 20:23   ` 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=Yh+sbYC5n4DsZWWg@redhat.com \
    --to=berrange@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=eduardo@habkost.net \
    --cc=kraxel@redhat.com \
    --cc=libvir-list@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 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).