From 3a1d80ad65df09e0fc0bbbe47effd3dd85213c01 Mon Sep 17 00:00:00 2001 From: Wesley van Tilburg Date: Sun, 4 Oct 2026 18:55:10 +0200 Subject: [PATCH] fedora-remote: add Mesa EGL for Proxmox virtio-gpu acceleration base-atomic ships mesa-dri-drivers (the virtio_gpu Gallium driver) but not mesa-libEGL, and with recommends off nothing pulls it in. mutter/gnome-shell only require libglvnd's EGL dispatcher, which then has no Mesa backend, so the session falls back to llvmpipe software rendering. Add mesa-libEGL explicitly so the host iGPU is used under Proxmox's VirGL/virtio-gpu display. --- images/fedora-remote/custom.yaml | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/images/fedora-remote/custom.yaml b/images/fedora-remote/custom.yaml index 2f106bb..444ee2e 100644 --- a/images/fedora-remote/custom.yaml +++ b/images/fedora-remote/custom.yaml @@ -23,6 +23,15 @@ packages: # Proxmox guest integration. - qemu-guest-agent + # Proxmox virtio-gpu display (VirGL): render on the host iGPU instead of + # software (llvmpipe). mesa-dri-drivers ships the virtio_gpu Gallium driver + # and comes from base-atomic; mesa-libEGL is the piece base-atomic lacks - it + # provides the Mesa EGL vendor, without which libglvnd's EGL dispatcher has no + # backend and mutter/gnome-shell fall back to software rendering. Listed + # explicitly (recommends are off) so the GL stack survives upstream changes. + - mesa-dri-drivers + - mesa-libEGL + # grd-firstboot generates the RDP TLS certificate with the openssl CLI. - openssl