Strange graphics bug when booting Fedora 34 Beta about homebrew-qemu-virgl HOT 18 CLOSED

Hi @oillipheist,

Yes, that's what I see as well. Just wanted to try out Gnome 40. This may or may not be the problem in the virgil3d integration, as Fedora is in beta.

I've tried to reach out to @akihikodaki (the author of macos virgil integration) but he said that he was unable to boot the aarch64 image of Fedora 34. Maybe things have changed and it's time to test it again.

from homebrew-qemu-virgl.

I got it booted and have done some basic investigation. Apparently the new version of Mesa adds new texture swizzling requirement to virtio-gpu-3d, which fails to meet it when displaying a texture. Later, I'll dig into the problem more to figure out a solution.

from homebrew-qemu-virgl.

I pushed a fix to GitHub (akihikodaki/qemu@43b8afe).

from homebrew-qemu-virgl.

@akihikodaki that's great! Thank you. I'll pull the patchset into the formula.

from homebrew-qemu-virgl.

@akihikodaki the new patch works for me when I use gl=core. But when I do gl=es, I see this:

Most of the windows are just slightly transparent red.

from homebrew-qemu-virgl.

@knazarov It was my fault. I have forgotten to push a part of the fix. I have just pushed it to my repository (akihikodaki/virglrenderer@01fcbb7).

gl=core is not affected by the problem so it should work even before applying the fix.

from homebrew-qemu-virgl.

@akihikodaki I've applied the patch, and now the texture is blue instead of red :)

from homebrew-qemu-virgl.

@knazarov Well, I suspect it is a bug of a lower layer (ANGLE, Intel driver and/or hardware). If you are interested, fiddle with: akihikodaki/virglrenderer@01fcbb7#diff-f9ec2e109236d40360f659ae49f3d1ad43f7608c6b62c0520a1765b850bb572dR10661

from homebrew-qemu-virgl.

core profile doesn't seem to work on M1 here at all, have it working on ubuntu but seems broken on both fedora 33 and fedora 34beta

from homebrew-qemu-virgl.

I have core profile work with Fedora 33. My command line is:

qemu-system-aarch64 -machine virt,accel=hvf,highmem=off -cpu cortex-a72 -smp 8 -m 14336 -drive if=pflash,format=raw,file=/Users/person/fedora/drive/edk2-aarch64-code.fd,readonly=on -drive if=pflash,format=raw,file=/Users/person/fedora/drive/edk2-arm-vars.fd,discard=on -drive id=virtio,if=none,format=raw,file=/Users/person/fedora/drive/virtio.raw,discard=on -device intel-hda -device hda-output -device virtio-gpu-pci -device virtio-net-device,netdev=net -device virtio-mouse-pci -device virtio-keyboard-pci -device virtio-blk-device,drive=virtio -device virtio-rng-device -display cocoa,gl=core -netdev user,id=net -full-screen -runas 501:20

from homebrew-qemu-virgl.

hmm.. Tried that and got

qemu-system-aarch64: Failed to setgroups(1, [20])

from homebrew-qemu-virgl.

@oillipheist

hmm.. Tried that and got

qemu-system-aarch64: Failed to setgroups(1, [20])

The command line requires root to run. Use sudo, or modify the command line (and please share it if you got the problem reproduced with.)

from homebrew-qemu-virgl.

@oillipheist I’ve merged @akihikodaki’s newer changeset to master, but I can’t check it, since I’m without a computer for at least 10 days.

from homebrew-qemu-virgl.

I’ve got my computer back, and will soon be trying Fedora 34, now that it’s released :)

from homebrew-qemu-virgl.

I added yet another fix to virglrenderer (see https://gist.github.com/akihikodaki/87df4149e7ca87f18dc56807ec5a1bc5#gistcomment-3722509 for details). I'll use Fedora 34 for daily use from now.

from homebrew-qemu-virgl.

I’ve pulled your fixes, thanks!

from homebrew-qemu-virgl.

not sure if it was due to this, but since i updated to the latest version now also the lightdm slick greater is working well - before it was just full screen gray and now there is a proper login window :)

from homebrew-qemu-virgl.

Fedora 34 now works with the latest patch and is quite smooth. Just checked it on my mac.

from homebrew-qemu-virgl.