Re: [OE-core][PATCH] qemu: upgrade 10.2.0 -> 11.0.0

[Quan Sun <Quan.Sun@windriver.com>]

On 5/29/26 8:42 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 Thu May 28, 2026 at 10:26 PM CEST, Quan Sun via lists.openembedded.org wrote:
>> From: Quan Sun <Quan.Sun@windriver.com>
>>
>> Upgrade QEMU to version 11.0.0.
>>
> Hi,
>
> Thanks for the new version.
>
> It looks like we are almost there, I now have just one selftest failing:
> 2026-05-29 08:23:23,583 - oe-selftest - INFO - runtime_test.TestImage.test_testimage_virgl_gtk_sdl (subunit.RemotedTestCase)
> 2026-05-29 08:23:23,584 - oe-selftest - INFO -  ... FAIL
> ...
> runqemu - ERROR - Failed to run qemu: qemu-system-x86_64: -qmp unix:./.i1y4asol,server,wait: info: QEMU waiting for connection on: disconnected:unix:./.i1y4asol,server=on
> qemu-system-x86_64: warning: host doesn't support requested feature: CPUID[eax=07h,ecx=00h].EBX.hle [bit 4]
> qemu-system-x86_64: warning: host doesn't support requested feature: CPUID[eax=07h,ecx=00h].EBX.rtm [bit 11]
> qemu-system-x86_64: warning: host doesn't support requested feature: CPUID[eax=07h,ecx=00h].EBX.hle [bit 4]
> qemu-system-x86_64: warning: host doesn't support requested feature: CPUID[eax=07h,ecx=00h].EBX.rtm [bit 11]
> qemu-system-x86_64: warning: host doesn't support requested feature: CPUID[eax=07h,ecx=00h].EBX.hle [bit 4]
> qemu-system-x86_64: warning: host doesn't support requested feature: CPUID[eax=07h,ecx=00h].EBX.rtm [bit 11]
> qemu-system-x86_64: warning: host doesn't support requested feature: CPUID[eax=07h,ecx=00h].EBX.hle [bit 4]
> qemu-system-x86_64: warning: host doesn't support requested feature: CPUID[eax=07h,ecx=00h].EBX.rtm [bit 11]
> glx: failed to create dri3 screen
> failed to load driver: vgem
>
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/35/builds/3924
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/3786
>
> Can you have a look at the issue?
>
> Thanks,
> Mathieu

Hi Mathieu,

It seems this issue is not caused by the qemu upgrade. I also asked an 
AI agent to carefully examine the build/test logs, and the following is 
what it says:

--- Root Cause ---

The only failing test is 
runtime_test.TestImage.test_testimage_virgl_gtk_sdl — and it
is NOT caused by the QEMU 10.2→11.0 upgrade. It's a GPU/graphics driver 
issue on the
autobuilder worker host.

The key error messages are:

glx: failed to create dri3 screen
failed to load driver: vgem


This means QEMU 11.0's virgl (GPU virtualization) display backend 
(-display gtk,gl=on)
failed because the autobuilder host (ubuntu2510-vk-1) doesn't have a 
working DRI3/GPU
driver setup. The vgem (Virtual GEM) driver failed to load, which 
prevents virgl from
initializing OpenGL, which causes QEMU to exit immediately before the 
QMP monitor
connection can be established.

--- Why this is NOT a QEMU upgrade regression ---

1. 685 out of 686 tests passed — including many other QEMU-based tests 
(runqemu boot
tests, testimage_dnf, testimage_install, testimage_slirp, 
testimage_virgl_headless,
etc.)
2. The test_testimage_virgl_headless test (virgl without GTK/SDL 
display) passed fine —
confirming QEMU itself works.
3. The failure is specifically in the GTK+SDL+GL display path, which 
requires a
functional GPU/DRI3 stack on the host.
4. This is a known class of intermittent/environment-dependent failure 
on CI workers
that lack proper GPU passthrough.

Please check if it's a pre-existing autobuilder infrastructure issue — 
the worker ubuntu2510-vk-1 doesn
't have a working DRI3 GPU driver for virgl's GTK/SDL/GL display mode. 
This test
may likely also fail (or maybe flaky) with QEMU 10.2 on that same worker.

Thanks,

Quan


>
> --
> Mathieu Dubois-Briand, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
>