From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org, "Peter Maydell" <peter.maydell@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
qemu-arm@nongnu.org, "Maxim Levitsky" <mlevitsk@redhat.com>,
libvir-list@redhat.com,
"Richard Henderson" <richard.henderson@linaro.org>,
xen-devel@lists.xenproject.org,
"Reinoud Zandijk" <reinoud@netbsd.org>,
"Michael S . Tsirkin" <mst@redhat.com>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>
Subject: Re: [PATCH 1/2] docs/about: Deprecate 32-bit x86 hosts and qemu-system-i386
Date: Mon, 27 Feb 2023 11:50:07 +0000 [thread overview]
Message-ID: <Y/yY72L9wyjuv3Yz@redhat.com> (raw)
In-Reply-To: <20230227111050.54083-2-thuth@redhat.com>
On Mon, Feb 27, 2023 at 12:10:49PM +0100, Thomas Huth wrote:
> Hardly anybody still uses 32-bit x86 hosts today, so we should
> start deprecating them to finally have less test efforts.
> With regards to 32-bit KVM support in the x86 Linux kernel,
> the developers confirmed that they do not need a recent
> qemu-system-i386 binary here:
>
> https://lore.kernel.org/kvm/Y%2ffkTs5ajFy0hP1U@google.com/
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> docs/about/deprecated.rst | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/docs/about/deprecated.rst b/docs/about/deprecated.rst
> index 15084f7bea..98517f5187 100644
> --- a/docs/about/deprecated.rst
> +++ b/docs/about/deprecated.rst
> @@ -196,6 +196,19 @@ CI coverage support may bitrot away before the deprecation process
> completes. The little endian variants of MIPS (both 32 and 64 bit) are
> still a supported host architecture.
>
> +32-bit x86 hosts and ``qemu-system-i386`` (since 8.0)
> +'''''''''''''''''''''''''''''''''''''''''''''''''''''
> +
> +Testing 32-bit x86 host OS support takes a lot of precious time during the
> +QEMU contiguous integration tests, and considering that most OS vendors
> +stopped shipping 32-bit variants of their x86 OS distributions and most
> +x86 hardware from the past >10 years is capable of 64-bit, keeping the
> +32-bit support alive is an inadequate burden for the QEMU project. Thus
> +QEMU will soon drop the support for 32-bit x86 host systems and the
> +``qemu-system-i386`` binary. Use ``qemu-system-x86_64`` (which is a proper
> +superset of ``qemu-system-i386``) on a 64-bit host machine instead.
I feel like we should have separate deprecation entries for the
i686 host support, and for qemu-system-i386 emulator binary, as
although they're related they are independant features with
differing impact. eg removing qemu-system-i386 affects all
host architectures, not merely 32-bit x86 host, so I think we
can explain the impact more clearly if we separate them.
How about something like....
32-bit x86 hosts
''''''''''''''''
Support for 32-bit x86 host deployments is increasingly uncommon in
mainstream Linux distributions given the widespread availability of
64-bit x86 hardware. The QEMU project no longer considers 32-bit
x86 support to be an effective use of its limited resources, and
thus intends to discontinue it.
Current users of QEMU on 32-bit x86 hosts should either continue
using existing releases of QEMU, with the caveat that they will
no longer get security fixes, or migrate to a 64-bit platform
which remains capable of running 32-bit guests if needed.
``qemu-system-i386`` binary removal
'''''''''''''''''''''''''''''''''''
The ``qemu-system-x86_64`` binary can be used to run 32-bit guests
by selecting a 32-bit CPU model, including KVM support on x86_64
hosts. Once support for the 32-bit x86 host platform is discontinued,
the ``qemu-system-i386`` binary will be redundant. Current users are
recommended to reconfigure their systems to use the ``qemu-system-x86_64``
binary.
Same point for the next patch about 32-bit arm vs qemu-system-arm
binary.
With 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:[~2023-02-27 11:51 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 11:10 [PATCH 0/2] Deprecate support for 32-bit x86 and arm hosts Thomas Huth
2023-02-27 11:10 ` [PATCH 1/2] docs/about: Deprecate 32-bit x86 hosts and qemu-system-i386 Thomas Huth
2023-02-27 11:50 ` Daniel P. Berrangé [this message]
2023-02-27 20:12 ` Michael S. Tsirkin
2023-02-27 20:21 ` Richard Henderson
2023-02-28 8:59 ` Michael S. Tsirkin
2023-02-28 12:26 ` Philippe Mathieu-Daudé
2023-02-28 9:00 ` Michael S. Tsirkin
2023-02-28 16:57 ` Richard Henderson
2023-02-27 22:32 ` Philippe Mathieu-Daudé
2023-02-28 7:43 ` Thomas Huth
2023-02-28 7:49 ` Thomas Huth
2023-02-28 8:19 ` Michael S. Tsirkin
2023-02-28 8:59 ` Daniel P. Berrangé
2023-02-28 9:03 ` Michael S. Tsirkin
2023-02-28 9:14 ` Thomas Huth
2023-02-28 9:40 ` Daniel P. Berrangé
2023-02-28 10:11 ` Michael S. Tsirkin
2023-02-28 10:39 ` Markus Armbruster
2023-02-28 10:51 ` Michael S. Tsirkin
2023-02-28 11:12 ` Thomas Huth
2023-02-28 11:24 ` Michael S. Tsirkin
2023-02-28 11:27 ` Daniel P. Berrangé
2023-02-28 11:34 ` Markus Armbruster
2023-02-28 11:45 ` Michael S. Tsirkin
2023-02-27 20:25 ` Richard Henderson
2023-02-28 7:52 ` Thomas Huth
2023-02-27 11:10 ` [PATCH 2/2] docs/about: Deprecate 32-bit arm hosts and qemu-system-arm Thomas Huth
2023-02-27 18:38 ` [PATCH 0/2] Deprecate support for 32-bit x86 and arm hosts Daniel P. Berrangé
2023-02-28 7:39 ` Thomas Huth
2023-02-28 9:01 ` Daniel P. Berrangé
2023-02-28 11:46 ` Michael S. Tsirkin
2023-02-28 20:05 ` Thomas Huth
2023-02-28 21:32 ` Michael S. Tsirkin
2023-03-01 6:38 ` Thomas Huth
2023-03-01 7:35 ` Markus Armbruster
2023-03-01 7:46 ` Warner Losh
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=Y/yY72L9wyjuv3Yz@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=libvir-list@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mlevitsk@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=reinoud@netbsd.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.com \
--cc=xen-devel@lists.xenproject.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).