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

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

On 5/29/26 11:23 AM, Alexander Kanavin 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 Fri, 29 May 2026 at 16:45, Quan Sun via lists.openembedded.org
> <Quan.Sun=windriver.com@lists.openembedded.org> wrote:
>>> 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?
>> 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:
> Unfortunately AI has produced a total hallucination in its analysis,
> because it looks only at the build log given to it, not at the actual
> change that is being tested (e.g. it wouldn't see in that log that
> there is a qemu update, and it wouldn't go and analyse the qemu own
> changelog and commit history, and it wouldn't run the same test
> against qemu 10.x to narrow it down and so on).
>
> I went and tried this test with qemu 10.x on the same host, and it
> passes just fine:
>
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/35/builds/3928
>
> Then I cherry picked the qemu 11.x patch, and the test then fails:
>
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/35/builds/3930
>
> It's still possible something is misconfigured on the host (it runs
> tiger vnc standalone server to allow X clients such as qemu to render
> into it), but the issue is clearly triggered by the version upgrade.
>
> Alex

Hi Alex,

I looked at your test logs and not sure if you performed the test by 
really using the qemu 11.0.0. (Note the QEMU binary used in the test was 
built from sstate cache (1851 of
1852 tasks were cached —
Sstate summary: Wanted 187 Local 187 ... 100% match, 100% complete), 
meaning it may have used
whatever QEMU version is already in master's sstate, not a freshly-built 
QEMU 11.0 ?)

Regardless of the AI agent, but the earlier test really failed on the 
worker ubuntu2510-vk-1 because that host lacks GPU/DRI3 drivers. Have 
you performed your test on this worker ubuntu2510-vk-1 ?

Thanks,

Quan