From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Helge Deller <deller@kernel.org>
Cc: qemu-devel@nongnu.org,
Richard Henderson <richard.henderson@linaro.org>,
Michael Tokarev <mjt@tls.msk.ru>
Subject: Re: [PATCH v3] Allow building qemu tools on 32-bit hosts
Date: Tue, 7 Apr 2026 11:00:01 +0100 [thread overview]
Message-ID: <adTVobzrgl8f6chd@redhat.com> (raw)
In-Reply-To: <adGTUNUSckx1KrAk@p100>
On Sun, Apr 05, 2026 at 12:40:16AM +0200, Helge Deller wrote:
> Qemu's tools like qemu-img are often needed on 32-bit platforms,
> although the actual qemu emulators have been discontinued on 32-bit.
IMHO, the thought behind disabling 32-bit builds was not making
a statement about whether the code was useful on 32-bit platforms.
Users of 32-bit platforms will naturally always want to have as
much as possible available on their platform.
Rather it was that 32-bit platforms were no longer considered
important as targets by QEMU maintainers. The goal is thus to
reduce the set of targets that maintainers have to think about.
Thus the commit message needs to be justifying why 32-bit platforms
should still be treated as a target.
In terms of the impact on QEMU maintainers / subsystems we see
* QEMU guest agent
=> util/, qapi/, qobject/, qom/, qga/
Total about 300 C files
* Adding in tools on top we also get
=> block/, chardev/, crypto/, io/, authz/, storage-daemon/
Total about 700 C files
I'll support the build of QEMU guest agent on 32-bit, as we were
clear that we wanted to continue supporting 32-bit guests in
general.
I'm not in favour of re-introducing 32-bit support for anything
else.
With regards,
Daniel
--
|: https://berrange.com ~~ https://hachyderm.io/@berrange :|
|: https://libvirt.org ~~ https://entangle-photo.org :|
|: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|
next prev parent reply other threads:[~2026-04-07 19:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-04 22:40 [PATCH v3] Allow building qemu tools on 32-bit hosts Helge Deller
2026-04-07 10:00 ` Daniel P. Berrangé [this message]
2026-04-13 7:29 ` Markus Armbruster
2026-04-13 8:28 ` Peter Maydell
2026-04-07 15:12 ` Michael Tokarev
2026-04-07 15:35 ` Helge Deller
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=adTVobzrgl8f6chd@redhat.com \
--to=berrange@redhat.com \
--cc=deller@kernel.org \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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 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.