All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>, Stefan Weil <sw@weilnetz.de>
Subject: Re: dropping 32-bit Windows host support
Date: Mon, 19 Feb 2024 15:53:21 +0000	[thread overview]
Message-ID: <ZdN5cbaqnJMTK5ts@redhat.com> (raw)
In-Reply-To: <CAFEAcA_BB5-eieVGuqqXn3aS-Vmc7OcTFmv5e=i5HgNw3Kp2FQ@mail.gmail.com>

On Mon, Feb 19, 2024 at 03:37:31PM +0000, Peter Maydell wrote:
> Our msys2 32-bit Windows host CI job has been failing recently
> because upstream MSYS2 are starting to phase out 32-bit windows
> host support and are steadily removing i686 versions of packages.
> The latest is dtc:
> https://gitlab.com/qemu-project/qemu/-/issues/2177
> 
> The writing is clearly on the wall for their 32-bit support, judging
> from the "2023-12-13 - Starting to drop some 32-bit Packages" news
> item at https://www.msys2.org/news/ and associated discussion at
> https://github.com/msys2/MINGW-packages/discussions/19326 .
> 
> QEMU on a 32-bit host is not likely to be a great experience, and I
> suspect we don't have many users using 32-bit Windows who couldn't
> use the 64-bit version instead. Our Download page points users at
> MSYS2's packages, and they have already dropped the 32-bit QEMU
> package build. Stefan Weil's binaries page, which is the other thing
> we link to from Download, has no 32-bit version newer than 7.2.0.
> So anybody using 32-bit Windows QEMU must be building it themselves.
> Plus, we've already deprecated system emulation on 32-bit x86 hosts,
> so the only remaining "supported" config is with the NVMM or WHPX
> accelerators.

The other data point is that Win11 is 64-bit only, and IIUC,
Win10 was 64-bit only for new OEM installs too, only upgrades
or end user installs could choose 32-bit. 

> 
> I suggest that we should:
> 
>  * remove the msys2-32bit CI job entirely (we will still have at least
>    compile-time coverage via the cross-win32-system job)
>  * document that the 32-bit Windows support is deprecated in
>    docs/about/build-platforms.rst and deprecated.rst
>  * update our Download page to remove mention of 32-bit Windows
> 
> Any objections?

I think that's sane.

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 :|



  reply	other threads:[~2024-02-19 15:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-19 15:37 dropping 32-bit Windows host support Peter Maydell
2024-02-19 15:53 ` Daniel P. Berrangé [this message]
2024-02-19 16:26   ` Thomas Huth
2024-02-19 16:40     ` Peter Maydell
2024-02-19 16:50       ` Daniel P. Berrangé
2024-02-19 19:32     ` Stefan Weil via

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=ZdN5cbaqnJMTK5ts@redhat.com \
    --to=berrange@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=sw@weilnetz.de \
    /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.