Make Omarchy usable in a VM without GPU acceleration
The problem is real and manual/49-omarchy-on.md acknowledges VirtualBox and VMware with the 'performance probably won't be great' caveat. But the technical framing and the fallback are obsolete. Hyprland is no longer a wlroots compositor. It moved to its own Aquamarine backend, and WLR_RENDERER_ALLOW_SOFTWARE is a dead wlroots variable: a code search across the entire hyprwm org returns zero occurrences of it (and zero for LIBGL_ALWAYS_SOFTWARE). Beyond being obsolete, the delivery mechanism cannot work: env/hl.env in monitors.conf/monitors.lua exports variables to clients Hyprland launches, but the compositor's own renderer reads its environment at process start, before the config is applied, so setting a software-rendering variable there cannot affect Hyprland's own startup. It must be set in the session environment before Hyprland launches. Minor: glxinfo -B needs mesa-utils (not mentioned), and journalctl --user -b -u hyprland matches nothing because under uwsm the unit is wayland-wm@hyprland.service.
LIBGL_ALWAYS_SOFTWARE=1 disables all GPU acceleration system-wide for the session. Remove it once real acceleration works, or video playback and browsers will stay unusable.
Symptom
Omarchy installed in VirtualBox / VMware / a generic QEMU VM boots to a black screen, or the desktop appears but is unusably slow: dragging a window takes seconds, animations stutter, video is a slideshow. Sometimes Hyprland exits immediately with an EGL/DRM error.
Cause
Hyprland requires a DRM device with working GL/EGL. Many hypervisor display adapters expose no usable 3D acceleration, so either no DRM node is found (black screen) or everything falls back to software rendering (slow). Note that Hyprland is no longer a wlroots compositor. It uses its own Aquamarine backend, so the old wlroots software-rendering escape hatches do not exist, and the compositor reads its environment at process start, before any config is applied, so a variable set from the Hyprland config cannot affect its own startup. Omarchy's own docs acknowledge VirtualBox works but "performance probably won't be great".
Fix
Confirm what the guest actually has. glxinfo comes from mesa-utils, and under uwsm the compositor's unit is wayland-wm@hyprland.service, not hyprland:
ls -l /dev/dri/
sudo pacman -S --needed mesa-utils
glxinfo -B | grep -E 'renderer|OpenGL version'
journalctl --user -b -u wayland-wm@hyprland.service --no-pager | tail -40
If /dev/dri/ is empty there is no DRM node at all and no environment variable will help. You must give the VM a virtual GPU.
**QEMU/KVM (best option):** give the guest virtio-gpu with venus/virgl and enough VRAM. In virt-manager set Video model to **Virtio** and tick **3D acceleration**, and set Display to **SPICE** with OpenGL enabled. In the guest:
sudo pacman -S --needed mesa vulkan-virtio qemu-guest-agent spice-vdagent
sudo systemctl enable --now qemu-guest-agent spice-vdagentd
**VirtualBox / VMware:** enable EFI, allocate 128 MB video memory, enable 3D acceleration, and install guest additions.
If you need software rendering, note that WLR_RENDERER_ALLOW_SOFTWARE does nothing. Hyprland dropped wlroots for its own Aquamarine backend and never reads that variable. Use the Mesa variable, and set it in the **session environment before Hyprland starts**, not in monitors.lua (variables set there go to the apps Hyprland launches, not to the compositor itself):
mkdir -p ~/.config/uwsm
echo 'export LIBGL_ALWAYS_SOFTWARE=1' >> ~/.config/uwsm/env
Then log out and back in. Expect llvmpipe-class performance.
Set a fixed resolution rather than preferred, because virtual displays often report a useless preferred mode. In ~/.config/hypr/monitors.lua:
hl.monitor({ output = "", mode = "1920x1080@60", position = "auto", scale = 1 })
Verify
ls /dev/dri/ shows a card0/renderD128 node, hyprctl monitors lists a monitor at the expected resolution, and window dragging is smooth.