On Fri, 29 May 2026 at 16:45, Quan Sun via lists.openembedded.org <[email protected]> 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
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#237761): https://lists.openembedded.org/g/openembedded-core/message/237761 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]] -=-=-=-=-=-=-=-=-=-=-=-
