qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>, qemu-devel@nongnu.org
Cc: Eduardo Habkost <eduardo@habkost.net>,
	Paolo Bonzini <pbonzini@redhat.com>,
	"Daniel P. Berrange" <berrange@redhat.com>
Subject: Re: [PATCH] hw/i386/pc_piix: Mark the machine types from version 1.4 to 1.7 as deprecated
Date: Tue, 15 Feb 2022 17:50:19 +0100	[thread overview]
Message-ID: <03217598-a05f-5d82-72a4-2016137d1161@redhat.com> (raw)
In-Reply-To: <20220117191639.278497-1-thuth@redhat.com>

On 17/01/2022 20.16, 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.
> 
> 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;

*ping*

Seems like the discussion about marking old machine types ceased very 
quickly ... but since nobody has written any concerns against this patch 
here, could we at least agree to apply this patch to get the deprecation 
timer started again for some machine types in 7.0 ?

  Thomas



      parent reply	other threads:[~2022-02-15 16:52 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é
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 [this message]

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=03217598-a05f-5d82-72a4-2016137d1161@redhat.com \
    --to=thuth@redhat.com \
    --cc=berrange@redhat.com \
    --cc=eduardo@habkost.net \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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).