From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: Eduardo Habkost <eduardo@habkost.net>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH] hw/i386/pc_piix: Mark the machine types from version 1.4 to 1.7 as deprecated
Date: Mon, 17 Jan 2022 20:12:16 +0000 [thread overview]
Message-ID: <YeXNoKzsFeIPSy6E@redhat.com> (raw)
In-Reply-To: <20220117191639.278497-1-thuth@redhat.com>
On Mon, Jan 17, 2022 at 08:16:39PM +0100, Thomas Huth wrote:
> The list of machine types grows larger and larger each release ... and
> it is unlikely that many people still use the very old ones for live
> migration. QEMU v1.7 has been released more than 8 years ago, so most
> people should have updated their machines to a newer version in those
> 8 years at least once. Thus let's mark the very old 1.x machine types
> as deprecated now.
What criteria did you use for picking v1.7 as the end point ?
I'm fine with the idea of aging out machine types, but I'd like us
to explain the criteria we use for this, so that we can set clear
expectations for users. I'm not a fan of adhoc decisions that have
different impact every time we randomly decide to apply them.
A simple rule could be time based - eg we could say
"we'll keep machine type versions for 5 years or 15 releases."
one factor is how long our downstream consumers have been keeping
machines around for.
In RHEL-9 for example, the oldest machine is "pc-i440fx-rhel7.6.0"
which IIUC is derived from QEMU 2.12.0. RHEL-9 is likely to rebase
QEMU quite a few times over the coming years, so that 2.12.0 version
sets an example baseline for how long machines might need to live for.
That's 4 years this April, and could potentially be 6-7 years by the
time RHEL-9 stops rebasing QEMU.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> docs/about/deprecated.rst | 8 ++++++++
> hw/i386/pc_piix.c | 1 +
> 2 files changed, 9 insertions(+)
>
> diff --git a/docs/about/deprecated.rst b/docs/about/deprecated.rst
> index e21e07478f..652a4d43b6 100644
> --- a/docs/about/deprecated.rst
> +++ b/docs/about/deprecated.rst
> @@ -318,6 +318,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.
>
> +``pc-i440fx-1.4`` up to ``pc-i440fx-1.7`` (since 7.0)
> +'''''''''''''''''''''''''''''''''''''''''''''''''''''
> +
> +These old machine types are quite neglected nowadays and thus might have
> +various pitfalls with regards to live migration. Use a newer machine type
> +instead.
> +
> +
> Backend options
> ---------------
>
> diff --git a/hw/i386/pc_piix.c b/hw/i386/pc_piix.c
> index d9b344248d..84f3633223 100644
> --- a/hw/i386/pc_piix.c
> +++ b/hw/i386/pc_piix.c
> @@ -757,6 +757,7 @@ static void pc_i440fx_1_7_machine_options(MachineClass *m)
> m->hw_version = "1.7.0";
> m->default_machine_opts = NULL;
> m->option_rom_has_mr = true;
> + m->deprecation_reason = "old and unattended - use a newer version instead";
> compat_props_add(m->compat_props, pc_compat_1_7, pc_compat_1_7_len);
> pcmc->smbios_defaults = false;
> pcmc->gigabyte_align = false;
> --
> 2.27.0
>
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 :|
next prev parent reply other threads:[~2022-01-17 20:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 19:16 [PATCH] hw/i386/pc_piix: Mark the machine types from version 1.4 to 1.7 as deprecated Thomas Huth
2022-01-17 20:12 ` Daniel P. Berrangé [this message]
2022-01-18 8:49 ` Thomas Huth
2023-09-13 6:33 ` Philippe Mathieu-Daudé
2023-09-13 8:26 ` Daniel P. Berrangé
2022-02-15 16:50 ` Thomas Huth
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=YeXNoKzsFeIPSy6E@redhat.com \
--to=berrange@redhat.com \
--cc=eduardo@habkost.net \
--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 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).