On 5/26/26 5:39 AM, Mathieu Dubois-Briand wrote:
CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know
the content is safe.
On Mon May 25, 2026 at 10:10 PM CEST, Quan Sun via lists.openembedded.org wrote:
From: Quan Sun <[email protected]>
Upgrade QEMU to version 11.0.0.
Main changes:
- Add python3-qemu-qmp recipe (0.0.6) as a separate package. The QMP
Python library was removed from the QEMU source tree in 11.0.0 and
split into its own upstream project. This is needed by
qemu-system-native for testimage integration.
Add an entry for this recipe in maintainers.inc.
- QEMU 11.0.0 has officially dropped all support for 32-bit host systems.
This includes the ability to build the system emulator (softmmu) on
any 32-bit host architecture. Add COMPATIBLE_HOST:class-target to
restrict target builds to 64-bit architectures.
Note: QEMU 11.0.0 still supports emulating 32-bit guest architectures
(such as qemu-system-i386 or qemu-system-arm) as long as they are
running on a 64-bit host.
- qemu-targets.inc: skip linux-user targets when HOST_ARCH is not in the
set of architectures supported by QEMU 11.0.0's linux-user mode
(64-bit only: aarch64, loongarch64, mips64, ppc64, riscv64, s390x,
sparc64, x86_64).
- Add --cpu=${TUNE_ARCH} to EXTRA_OECONF for class-target, and add
--cpu=${SDK_ARCH} to nativesdk configure options to fix build
failure. QEMU 11's configure script falls back to 'uname -m' (x86_64)
when it cannot detect the host CPU.
- Add 0012-meson-fix-close_range-detection-on-older-glibc.patch:
the meson has_function('close_range') check succeeds at link time on
hosts with kernel >= 5.9 even when glibc < 2.34 does not declare the
function, causing implicit declaration errors. Add a prefix include
so the check only succeeds when the header declares close_range().
- Add
0013-hw-scsi-vhost-scsi-include-standard-headers-for-vhost-worker-structs.patch:
on build hosts with kernel headers < 6.0, vhost-scsi.c fails to
compile due to missing struct vhost_vring_worker/vhost_worker_state.
Include QEMU's bundled standard-headers before the system header,
matching the pattern already used in hw/virtio/vhost-backend.c.
- Drop fix-strerrorname_np.patch (fixed upstream).
Drop 0001-linux-user-elfload.c-Correction-to-HWCAP2-accessor.patch
(fixed upstream).
Drop 0001-accel-tcg-Fix-iotlb_to_section-for-different-Address.patch
(fixed upstream).
AI-Generated: kiro-cli
Signed-off-by: Quan Sun <[email protected]>
Hi,
Thanks for your patch.
I believe it is the source of the following build error on the
autobuilder:
ERROR: nativesdk-qemu-11.0.0-r0 do_configure: Execution of
'/srv/pokybuild/yocto-worker/qemuarm/build/build/tmp/work/i686-nativesdk-pokysdk-linux/nativesdk-qemu/11.0.0/temp/run.do_configure.2116027'
failed with exit code 1
...
| ERROR: Unknown CPU family i386, see
https://wiki.yoctoproject.org/wiki/Meson/UnknownCPU for directions.
|
| ERROR: meson setup failed
https://autobuilder.yoctoproject.org/valkyrie/#/builders/16/builds/3829
https://autobuilder.yoctoproject.org/valkyrie/#/builders/30/builds/3785
https://autobuilder.yoctoproject.org/valkyrie/#/builders/36/builds/3801
https://autobuilder.yoctoproject.org/valkyrie/#/builders/40/builds/3782
Can you have a look at the issue?
Thanks,
Mathieu
Hi Mathieu,
There is a major difference from earlier QEMU version: the QEMU 11.0.0
no longer supports 32-bit x86 as a host (see the (above) commit message
for more). I'll add COMPATIBLE_HOST:class-nativesdk with the 64-bit
architecture restriction later. This will prevent nativesdk-qemu from
attempting to build for i686 (SDKMACHINE), which QEMU 11.0.0 no longer
supports.
Note: this means the autobuilder configurations that use e.g. SDKMACHINE
= "i686" will no longer include qemu in the SDK.
Thanks,
Quan
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#237613):
https://lists.openembedded.org/g/openembedded-core/message/237613
Mute This Topic: https://lists.openembedded.org/mt/119486545/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
