Skip to content

Instantly share code, notes, and snippets.

@peppergrayxyz
Last active February 18, 2026 12:49
Show Gist options
  • Select an option

  • Save peppergrayxyz/fdc9042760273d137dddd3e97034385f to your computer and use it in GitHub Desktop.

Select an option

Save peppergrayxyz/fdc9042760273d137dddd3e97034385f to your computer and use it in GitHub Desktop.
QEMU with VirtIO GPU Vulkan Support

QEMU with VirtIO GPU Vulkan Support

With its latest reales qemu added the Venus patches so that virtio-gpu now support venus encapsulation for vulkan. This is one more piece to the puzzle towards full Vulkan support.

An outdated blog post on clollabora described in 2021 how to enable 3D acceleration of Vulkan applications in QEMU through the Venus experimental Vulkan driver for VirtIO-GPU with a local development environment. Following up on the outdated write up, this is how its done today.

Definitions

Let's start with the brief description of the projects mentioned in the post & extend them:

  • QEMU is a machine emulator
  • VirGL is an OpenGL driver for VirtIO-GPU, available in Mesa.
  • Venus is an experimental Vulkan driver for VirtIO-GPU, also available in Mesa.
  • Virglrenderer is a library that enables hardware acceleration to VM guests, effectively translating commands from the two drivers just mentioned to either OpenGL or Vulkan.
  • libvirt is an API for managing platform virtualization
  • virt-manager is a desktop user interface for managing virtual machines through libvirt

Merged Patches:

Work in progress:

Prerequisites

Make sure you have the proper version installed on the host:

  • linux kernel >= 6.13 built with CONFIG_UDMABUF
  • working Vulkan and kvm setup
  • qemu >= 9.2.0
  • virglrenderer with enabled venus support
  • mesa >= 24.2.0

You can verify this like so:

$ uname -r
6.13.0
$ ls /dev/udmabuf
/dev/udmabuf
$ ls /dev/kvm
/dev/kvm
$ qemu-system-x86_64 --version
QEMU emulator version 9.2.0
Copyright (c) 2003-2024 Fabrice Bellard and the QEMU Project developers

Check your distros package sources how they build virglrenderer.

For Vulkan to work you need the proper drivers to be installed for your graphics card.

To verfiy your setup, install vulkan-tools. Make sure mesa >= 24.2.0 and test vkcube:

$ vulkaninfo --summary | grep driverInfo
	driverInfo         = Mesa 24.2.3-1ubuntu1
	driverInfo         = Mesa 24.2.3-1ubuntu1 (LLVM 19.1.0)
...
$ vkcube
Selected GPU x: ..., type: ...

Building qemu

If your distro doesn't (yet) ship and updated version of qemu, you can build it yourself from source:

wget https://download.qemu.org/qemu-9.2.0.tar.xz
tar xvJf qemu-9.2.0.tar.xz
cd qemu-9.2.0
mkdir build && cd build
../configure --target-list=x86_64-softmmu  \
  --enable-kvm                 \
  --enable-opengl              \
  --enable-virglrenderer       \
  --enable-gtk                 \
  --enable-sdl
make -j4

The configuration step will throgh errors if packages are missing. Check the qemu wiki for further info what to install: https://wiki.qemu.org/Hosts/Linux

Create and run an image for QEMU

Create an image & fetch the distro of your choice:

Host

ISO=ubuntu-24.10-desktop-amd64.iso  
wget https://releases.ubuntu.com/oracular/ubuntu-24.10-desktop-amd64.iso  

IMG=ubuntu-24-10.qcow2
qemu-img create -f qcow2 $IMG 16G

Run a live version or install the distro

qemu-system-x86_64                                               \
    -enable-kvm                                                  \
    -M q35                                                       \
    -smp 4                                                       \
    -m 4G                                                        \
    -cpu host                                                    \
    -net nic,model=virtio                                        \
    -net user,hostfwd=tcp::2222-:22                              \
    -device virtio-vga-gl,hostmem=4G,blob=true,venus=true        \
    -vga none                                                    \
    -display gtk,gl=on,show-cursor=on                            \
    -usb -device usb-tablet                                      \
    -object memory-backend-memfd,id=mem1,size=4G                 \
    -machine memory-backend=mem1                                 \
    -hda $IMG                                                    \
    -cdrom $ISO                                                  

Adjust the parameters accordingly:

  • smp: number of cpu cores
  • m: RAM
  • hostmem,size: VRAM

Guest

Install mesa-utilites and vulkan-tools to test the setup:

$ glxinfo -B
$ vkcube
Selected GPU x: ..., type: ...

If the deive is llvmpipe somehting is wrong. The device should be virgl (...).

Troubleshooting

  • (host) add -d guest_errors to show error messages from the guest
  • (guest) try installing vulkan virtio drivers and mesa
  • check the original blog post

Ubuntu 24.10

This is how you do it on Ubuntu

kernel

Install mainline: https://github.com/bkw777/mainline

sudo add-apt-repository ppa:cappelikan/ppa
sudo apt update
sudo apt install mainline

find the latest kernel (>= 6.13), at the time of writing 6.13 is a release candidate, so include those:

$ mainline check --include-rc

Install kernel:

$ sudo mainline install 6.13-rc1

Verfify installed kernels:

$ mainline list-installed
mainline 1.4.10
Installed Kernels:
linux-image-6.11.0-13-generic
linux-image-generic-hwe-24.04
linux-image-unsigned-6.13.0-061300rc1-generic
mainline: done

reboot into new kernel

verify running kernel

$ uname -r
6.13.0-061300rc1-generic

virglrenderer

the ubuntu package is not compiled with the proper flags.

If installed remove it: $ sudo apt-get remove libvirglrenderer-dev

download, build & install from source with venus enabled

wget    https://gitlab.freedesktop.org/virgl/virglrenderer/-/archive/1.1.0/virglrenderer-1.1.0.tar.gz
sudo apt-get install python3-full ninja-build libvulkan-dev libva-dev
python3 -m venv venv
venv/bin/pip install meson
venv/bin/meson build -Dvideo=true -Dvenus=true
ninja -C build
ninja install

qemu

install qemu >= 9.2.0, at the time of writing ubuntu has not yet packaged it

Install build depdencies: https://wiki.qemu.org/Hosts/Linux

sudo apt-get install build-essential pip libslirp-dev slirp
sudo apt-get install git libglib2.0-dev libfdt-dev libpixman-1-dev zlib1g-dev ninja-build
sudo apt-get install git-email
sudo apt-get install libaio-dev libbluetooth-dev libcapstone-dev libbrlapi-dev libbz2-dev
sudo apt-get install libcap-ng-dev libcurl4-gnutls-dev libgtk-3-dev
sudo apt-get install libibverbs-dev libjpeg8-dev libncurses5-dev libnuma-dev
sudo apt-get install librbd-dev librdmacm-dev
sudo apt-get install libsasl2-dev libsdl2-dev libseccomp-dev libsnappy-dev libssh-dev
sudo apt-get install libvde-dev libvdeplug-dev libvte-2.91-dev libxen-dev liblzo2-dev
sudo apt-get install valgrind xfslibs-dev 
sudo apt-get install libnfs-dev libiscsi-dev

build and run as described

virt-manager

-- work in progress --

Currently this is work in progress, so there is no option to add vulkan support in virt-manager. There are no fields to configure this. Also xml doesnt work, because libvirt doesn't know about these options either, so xml validation fails. There is however an option for QEMU command-line passthrough which bypasses the validation.

If you setup a default machine with 4G of memory, you can do this:

  <qemu:commandline>
    <qemu:arg value="-device"/>
    <qemu:arg value="virtio-vga-gl,hostmem=4G,blob=true,venus=true"/>
    <qemu:arg value="-object"/>
    <qemu:arg value="memory-backend-memfd,id=mem1,size=4G"/>
    <qemu:arg value="-machine"/>
    <qemu:arg value="memory-backend=mem1"/>
    <qemu:arg value="-vga"/>
    <qemu:arg value="none"/>
  </qemu:commandline>

Which gives this error:

qemu-system-x86_64: virgl could not be initialized: -1

Changing the number from 4G to 4194304k (same as memory) leds to this error:

qemu-system-x86_64: Spice: ../spice-0.15.2/server/red-qxl.cpp:435:spice_qxl_gl_scanout: condition `qxl_state->gl_draw_cookie == GL_DRAW_COOKIE_INVALID' failed

to be further investigated.

@DocMAX
Copy link

DocMAX commented Feb 3, 2026

Is this bug QEMU or MESA?

TigerVNC/tigervnc#2058

@the-burrito-triangle
Copy link

the-burrito-triangle commented Feb 5, 2026

So I did some more testing, and everything is "working" but the host GPU is stuck at its idle frequency of 450 MHz which is why glmark2-wayland and vkmark get such low scores and why using llvmpipe on the guest scores higher (800+ in glmark2 and 450+ in vkmark). Also, there is a bug in the latest mesa-git (on the guest OS) where glmark2-wayland scores fall off a cliff (drop from 450 to 200). And then there is a QEMU bug with the GTK3 display where if the host has a display scale greater than 100% the cursor is made too large in the guest OS. Bugs, everywhere it seems.

The cursor bug isn't all that important, but the host GPU being stuck at idle is killing VirGL and Venus guest performance.

Is there a reason everyone is using virtio-vga-gl? When testing, I got better performance when using virtio-gpu-gl-pci and going into the UEFI firmware and setting the OVMF Platform Configuration display to 4k resolution (although there seems to be a bug here as well with display scaling on the host OS, as it resizes to half the display in the UEFI firmware). The virtio-vga options max-out at 1920x1080 in the UEFI firmware, while the virtio-gpu versions go above 4k.

Screenshot 2026-02-04 23-12-38

Here're some tests with a CachyOS live installer guest with the Linux host running Niri with 200% display scale on a 4k monitor. qmassa is open on the host OS and is showing the iGPU load and its clockspeed--which never changes. Note the max clockspeed of 1300 MHz and the current speed of 450 MHz, which is the idle clockspeed.


$ sudo dmesg | grep -iE "drm|virtio-gpu|virtio-pci"
[    0.331789] ACPI: bus type drm_connector registered
[    0.811334] [drm] pci: virtio-gpu-pci detected at 0000:00:03.0
[    0.811512] [drm] Host memory window: 0x7000000000 +0x20000000
[    0.811514] [drm] features: +virgl +edid +resource_blob +host_visible
[    0.811515] [drm] features: +context_init
[    0.812813] [drm] number of scanouts: 1
[    0.812818] [drm] number of cap sets: 3
[    0.816432] [drm] cap set 0: id 1, max-version 1, max-size 308
[    0.816604] [drm] cap set 1: id 2, max-version 2, max-size 1408
[    0.816649] [drm] cap set 2: id 4, max-version 0, max-size 160
[    0.816827] virtio-pci 0000:00:03.0: [drm] Registered 1 planes with drm panic
[    0.816830] [drm] Initialized virtio_gpu 0.1.0 for 0000:00:03.0 on minor 0
[    0.856578] virtio-pci 0000:00:03.0: [drm] fb0: virtio_gpudrmfb frame buffer device
[    6.386700] systemd[1]: Load Kernel Module drm was skipped because of an unmet condition check (ConditionKernelModuleLoaded=!drm).

$ lsmod | grep -i virtio_gpu
virtio_gpu            114688  3
virtio_dma_buf         12288  1 virtio_gpu
Screenshot 2026-02-04 22-44-21

When running a Vulkan benchmark we see virgilrenderer open on the host OS but the idle clockspeed of the iGPU kills perf.

Screenshot 2026-02-04 22-43-04 Screenshot 2026-02-04 22-48-45

@fproverbio
Copy link

Has anybody managed to use video decoding/encoding using virgl/venus? both vainfo and vulkaninfo | grep VK_KHR_video return nothing even if the card (rx7800 xt) works in the vm (i can run vkcube fine). Phoronix reported on it a long while ago, so it should be merged into qemu/mesa normal release. Leaving the articles for reference:

encoding
decoding

@the-burrito-triangle
Copy link

From what I understand, only vDRM / "native context" will do video encode/decode via Vulkan Video. VA-API will not work. Native context is supported on AMD and very recently on Intel. Native Context is way better than Venus + VirGL or Venus + Zink.

Dmitry Osipenko
@digetx 2 weeks ago
Author Contributor

Thanks for testing! Video dec/enc available with Vulkan video. Intel-media-driver isn't a part of Mesa, it doesn't support native context - hence vaapi not supported unless somebody will volunteer to work on nctx for it.

https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/29870

https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/21658

@fproverbio
Copy link

From what I understand, only vDRM / "native context" will do video encode/decode via Vulkan Video. VA-API will not work. Native context is supported on AMD and very recently on Intel. Native Context is way better than Venus + VirGL or Venus + Zink.

Dmitry Osipenko
@digetx 2 weeks ago
Author Contributor
Thanks for testing! Video dec/enc available with Vulkan video. Intel-media-driver isn't a part of Mesa, it doesn't support native context - hence vaapi not supported unless somebody will volunteer to work on nctx for it.

https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/29870

https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/21658

i see, i've found a sort of checklist to enable native context in a patchset (link).

on host:

  • linux 6.13 onwards for host blob support
  • virglrenderer built with -Dvenus=true -Drender-server=true for vulkan passthrough (venus)
  • virglrenderer built with -Ddrm-renderers=amdgpu-experimental (native context AMDGPU only)
  • virglrenderer built with -Ddrm-renderers=i915-experimental 'mr1384' (native context i915) mr 1384

guest requirements

  • 16.0 onwards mesa already has stuff for opengl passthrough
  • 24.2 onwards mesa already has stuff for vulkan passthrough (if not, build with -Dvulkan-drivers=virtio)
  • amdgpu native context: 25.0 onwards and built with Dgallium-drivers=radeonsi -Dvulkan-drivers=amd -Damdgpu-virtio=true
  • intel i915 native context: mr29870 built with -Dgallium-drivers=iris -Dvulkan-drivers=intel -Dintel-virtio-experimental=true

the patchset is pretty old (february 2025) so it might have been merged, i'll check if cachyos currently uses these build flags for all components.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment