other: 0.906
device: 0.901
graphic: 0.866
PID: 0.723
performance: 0.720
permissions: 0.703
files: 0.698
semantic: 0.658
debug: 0.538
network: 0.533
boot: 0.479
vnc: 0.452
socket: 0.354
KVM: 0.351

[QEMU User-Mode] Mesa Fails To Load RadeonSI Driver When In Docker Image

# System Details
AMD Ryzen 7 3700U
Ubuntu 20.04 Focal Focus

# Dockerfile

FROM arm32v7/debian:bullseye

RUN apt-get update && apt-get install -y mesa-utils

ENTRYPOINT glxgears

# Instructions For Reproduction
1. Install Docker
2. Build Docker Image: docker build --tag mesa-arm-test .
3. Run: docker run -v /tmp/.X11-unix:/tmp/.X11-unix --device /dev/dri:/dev/dri -e "DISPLAY=${DISPLAY}" mesa-arm-test

The Output Is:

amdgpu_device_initialize: amdgpu_query_info(ACCEL_WORKING) failed (-38)
amdgpu: amdgpu_device_initialize failed.
libGL error: failed to create dri screen
libGL error: failed to load driver: radeonsi
libGL error: failed to get magic
libGL error: failed to load driver: radeonsi

It then appears to run using software rendering.

I think you definitely need to provide more information ... how do you run QEMU? Which QEMU version? etc. ... Anyway:

The QEMU project is currently moving its bug tracking to another system.
For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting the bug state to "Incomplete" now.

If the bug has already been fixed in the latest upstream version of QEMU,
then please close this ticket as "Fix released".

If it is not fixed yet and you think that this bug report here is still
valid, then you have two options:

1) If you already have an account on gitlab.com, please open a new ticket
for this problem in our new tracker here:

    https://gitlab.com/qemu-project/qemu/-/issues

and then close this ticket here on Launchpad (or let it expire auto-
matically after 60 days). Please mention the URL of this bug ticket on
Launchpad in the new ticket on GitLab.

2) If you don't have an account on gitlab.com and don't intend to get
one, but still would like to keep this ticket opened, then please switch
the state back to "New" or "Confirmed" within the next 60 days (other-
wise it will get closed as "Expired"). We will then eventually migrate
the ticket automatically to the new system (but you won't be the reporter
of the bug in the new system and thus you won't get notified on changes
anymore).

Thank you and sorry for the inconvenience.


[Expired for QEMU because there has been no activity for 60 days.]