From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: "QEMU Development" <qemu-devel@nongnu.org>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Pierrick Bouvier" <pierrick.bouvier@linaro.org>
Subject: Re: QEMU requires a 64-bit CPU host architecture?
Date: Wed, 25 Mar 2026 09:18:13 +0000 [thread overview]
Message-ID: <acOoVWw3jXfkfion@redhat.com> (raw)
In-Reply-To: <fc32bb67-ea52-4244-9ad7-c18db3be339e@tls.msk.ru>
On Wed, Mar 25, 2026 at 11:08:41AM +0300, Michael Tokarev wrote:
> On 20.03.2026 09:45, Michael Tokarev wrote:
> > Hi!
> >
> > Is it intentional that qemu does not build utilities on 32bit hosts
> > anymore?
>
> This is
>
> commit 372ec46b9f1215f48a4717f2b7ed969f65bfadc6
> Author: Richard Henderson <richard.henderson@linaro.org>
> Date: Thu Dec 18 09:56:27 2025 +1100
>
> meson: Reject 32-bit hosts
>
> 32-bit hosts have been deprecated since 10.0.
>
> How would one build qemu-img and especially qemu-guest-agent, say,
> on i386 or armhf?
>
> I tried removing this error message from meson.build (in $subject),
> but it fails to build even the qga due to errors in atomic.h, -
> even if these aren't used by qga.
>
> That smells like a bad decision, - to drop qga and qemu-img support
> on 32bit architectures. Especially qga.
IMHO dropping the block related tools is reasonable, as if you keep
that, the dependencies that need to remain 32-bit compatible ripple
out across a very large part of the codebase.
Not having qga though feels like a pretty undesirable consequence,
given our message overall is that we were dropping host support but
keeping 32-bit emulation.
IMHO, the qga probably ought to be a separate project, but it has
a core dependancy on the QAPI code generator, and some of the related
shared C code (qobject/, qapi/ and some parts of util/), but even that
is quite a tangled web of deps.
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-03-25 9:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 6:45 QEMU requires a 64-bit CPU host architecture? Michael Tokarev
2026-03-20 8:54 ` Daniel P. Berrangé
2026-03-20 9:26 ` Helge Deller
2026-03-25 8:08 ` Michael Tokarev
2026-03-25 9:18 ` Daniel P. Berrangé [this message]
2026-03-25 10:24 ` Peter Maydell
2026-03-25 11:21 ` Philippe Mathieu-Daudé
2026-03-25 11:31 ` Daniel P. Berrangé
2026-03-25 11:55 ` Philippe Mathieu-Daudé
2026-03-25 13:05 ` Michael Tokarev
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=acOoVWw3jXfkfion@redhat.com \
--to=berrange@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=philmd@linaro.org \
--cc=pierrick.bouvier@linaro.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox