qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Stefan Weil <sw@weilnetz.de>
Cc: "Markus Armbruster" <armbru@redhat.com>,
	"Thomas Huth" <thuth@redhat.com>,
	qemu-devel@nongnu.org, "Peter Maydell" <peter.maydell@linaro.org>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	libvir-list@redhat.com, "Paolo Bonzini" <pbonzini@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Reinoud Zandijk" <reinoud@netbsd.org>,
	"Ryo ONODERA" <ryoon@netbsd.org>,
	"Brad Smith" <brad@comstyle.com>
Subject: Re: [RFC PATCH] docs/about/deprecated: Deprecate 32-bit host systems
Date: Fri, 17 Feb 2023 11:47:39 +0000	[thread overview]
Message-ID: <Y+9pW43XDp1qt7T6@redhat.com> (raw)
In-Reply-To: <39bc9b17-e6f2-ed1b-0d6d-31bbb98842cf@weilnetz.de>

On Fri, Feb 17, 2023 at 12:05:46PM +0100, Stefan Weil wrote:
> On Fri, Feb 17, 2023 at 11:36:41AM +0100, Markus Armbruster wrote:
> 
> > Which 32-bit hosts are still useful, and why?
> 
> 
> Citing my previous mail:
> 
>    I now checked all downloads of the latests installers since 2022-12-30.
> 
>    qemu-w32-setup-20221230.exe – 509 different IP addresses
>    qemu-w64-setup-20221230.exe - 5471 different IP addresses
> 
>    339 unique IP addresses are common for 32- and 64-bit, either
>    crawlers or people who simply got both variants. So there remain 170
>    IP addresses which only downloaded the 32-bit variant in the last week.
> 
>    I see 437 different strings for the browser type, but surprisingly
>    none of them looks like a crawler.
> 
> So there still seems to be a certain small need for QEMU installers for
> 32-bit Windows: 170 users für 32 bit only, 339 users for both 32 and 64 bit,
> 5132 users for 64 bit only.

The question which is hard/impossible to answer is whether the people
who downloaded the 32-bit build genuinely needed a 32-bit build or
just did so out of habit or confusion.

I know you can't believe everything you see with statistics, but as an
example, the chart at the bottom of this page suggests new deployments
of 32-bit Windows are negligible today:

    https://www.pcbenchmarks.net/os-marketshare.html

there are existing deployments not accounted for there, but that may
still suggest many of the 32-bit downloads of QEMU will end up being
run on 64-bit hosts.

If we were to apply our support platform rule of only targetting the
latest 2 versions of the OS, this limits our targets to Win 10 and
Win 11. Windows 11 dropped 32-bit IIUC, so we're talking about
32-bit installs of Windows 10 only - even in Win10 days all new
physical hardware would have been 64-bit capable.

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



  parent reply	other threads:[~2023-02-17 11:48 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-30 11:44 [RFC PATCH] docs/about/deprecated: Deprecate 32-bit host systems Thomas Huth
2023-01-30 11:47 ` Peter Maydell
2023-01-30 12:01   ` Daniel P. Berrangé
2023-01-30 12:22     ` Thomas Huth
2023-01-30 12:43       ` Daniel P. Berrangé
2023-01-30 13:07         ` Thomas Huth
2023-01-30 19:19     ` Richard Henderson
2023-01-30 23:14       ` Philippe Mathieu-Daudé
2023-01-30 23:33         ` Richard Henderson
2023-01-31  0:19           ` Philippe Mathieu-Daudé
2023-01-30 20:45     ` Alex Bennée
2023-02-05 22:12       ` Mark Cave-Ayland
2023-04-04 14:00         ` Thomas Huth
2023-04-04 14:20           ` Cédric Le Goater
2023-04-04 15:58             ` BALATON Zoltan
2023-04-04 14:32           ` Cédric Le Goater
2023-04-04 15:42             ` BALATON Zoltan
2023-04-05  8:01               ` Thomas Huth
2023-04-05 11:54                 ` BALATON Zoltan
2023-04-05 12:51                   ` Thomas Huth
2023-04-04 15:50           ` BALATON Zoltan
2023-04-05 21:01           ` Mark Cave-Ayland
2023-02-22  9:11       ` Bernhard Beschow
2023-02-22  9:51         ` Daniel P. Berrangé
2023-02-22 12:28           ` Reinoud Zandijk
2023-02-22 13:37             ` Alex Bennée
2023-02-17 10:36 ` Markus Armbruster
2023-02-17 10:40   ` Daniel P. Berrangé
2023-02-17 10:45   ` Claudio Fontana
2023-02-17 10:47   ` Daniel P. Berrangé
2023-02-17 11:05     ` Stefan Weil via
2023-02-17 11:43       ` Markus Armbruster
2023-02-17 11:47       ` Daniel P. Berrangé [this message]
2023-02-19 11:27       ` Reinoud Zandijk
2023-02-19 12:12         ` Stefan Weil via
2023-02-17 16:38     ` Paolo Bonzini
2023-02-17 17:43       ` Philippe Mathieu-Daudé
2023-02-17 18:57         ` Thomas Huth
2023-02-18 22:54           ` Jiaxun Yang
2023-02-17 19:49       ` Thomas Huth
2023-02-17 16:06   ` Reinoud Zandijk
2023-02-17 17:20     ` Daniel P. Berrangé
2023-02-17 18:22     ` Richard Henderson
2023-02-19 11:07       ` Reinoud Zandijk
2023-02-17 11:09 ` Claudio Fontana

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+9pW43XDp1qt7T6@redhat.com \
    --to=berrange@redhat.com \
    --cc=armbru@redhat.com \
    --cc=brad@comstyle.com \
    --cc=libvir-list@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=reinoud@netbsd.org \
    --cc=richard.henderson@linaro.org \
    --cc=ryoon@netbsd.org \
    --cc=stefanha@redhat.com \
    --cc=sw@weilnetz.de \
    --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).