Mesa 26.1 supports Vulkan 1.4 and accelerates graphics in virtual machines

Key points:
  • Full support for the new Vulkan 1.4 graphics API in the main drivers on the market: ANV, RADV, NVK, HoneyKrisp and Turnip.
  • Implementation of VirtIO-GPU in Intel drivers, allowing virtual machines to send direct commands to the physical graphics card.
  • The Zink translator driver enables hardware acceleration support for OpenGL ES 2.0 on PowerVR devices that are exclusively compatible with Vulkan.
  • The Rusticl OpenCL driver now requires a statically linked C++ standard library to avoid runtime conflicts.
  • VirGL has been left unmaintained and will be permanently removed from the codebase if a new maintainer is not found.

3D table, linux drivers

A few days ago the development team behind the Mesa project made it known through an announcement the availability of the experimental version 26.1.0, which represents the reference open source implementation for the OpenGL and Vulkan graphics APIs.

This preliminary update It marks a massive leap forward by incorporating full compatibility with the specification Vulkan 1.4 in the main controllers on the market. Among those benefiting are the ANV (Intel), RADV (AMD), NVK (NVIDIA), HoneyKrisp (Apple), and Turnip (Qualcomm) controllers.

Beyond protocol updates, this release radically transforms how virtualized environments interact with physical hardware and restructures support for low-power devices. With the introduction of virtual machine acceleration, the strategic expansion of OpenGL through translators like Zink, and the imminent removal of obsolete drivers like VirGL, Mesa 26.1.0 not only adds new features but also cleans up its codebase to pave the way for its future stable release for production environments.

Graphics acceleration in virtual machines

Uno of the most outstanding advances in this installment is Implementation of direct GPU access for virtual machines through the VirtIO-GPU protocol, initially available for Intel drivers (Iris, Crocus, and ANV). Previously, when a virtual machine (the "guest" system) needed to render 3D graphics, it had to translate and send the graphics commands through multiple layers of emulation and intermediate protocols until they reached the host operating system (the "host"), which generated considerable latency and limited the performance of demanding games or applications.

With the Implementing VirtIO-GPU access eliminates this bottleneck. The The guest system can now package graphical commands in its native format and transmit them directly to the host's physical graphics card, bypassing emulationThis technology radically transforms the performance of virtual GPUs, allowing you to play games and run heavy software inside a virtual machine with performance almost identical to that obtained in a native environment.

Support for OpenGL is also expanding into mobile and low-power architectures. The controller Zink has enabled support for OpenGL ES 2.0 over PowerVR hardware, enabling hardware acceleration on modern devices that natively only support the Vulkan API. Additionally, the driver Panfrost, designed for the ARM Mali architecture, It assimilates the GL_EXT_shader_image_load_store extension.Meanwhile, the AMD and Broadcom drivers add support for critical semaphore and shading extensions.

The decline of VirGL and modern standardization

All this modernization brings with it the inevitable obsolescence of legacy components that no longer meet current performance standards. VirGL driver, which for years served as the cornerstone for implementing virtual GPUs within the QEMU emulator, It has been officially declared maintenance-free..

El Mesa's team has warned that if no external developer offers to take responsibility for their code in the short term, VirGL will be permanently removed from the main branch. This decision underscores the project's absolute confidence in the new VirtIO-GPU ecosystem and marks the end of an era in open-source graphics virtualization, forcing the industry to transition to much more efficient and straightforward protocols.

Finally, if you are interested in knowing more about it, you can consult the details in the following link

How to install Mesa drivers on Linux?

The Mesa packages are found in all Linux distributions, so its installation can be done either by downloading and compiling the source code (All the information about it herei) or in a relatively simple way, which depends on availability within the official channels of your distribution or third parties.

For those who are Ubuntu, Debian or derivatives users, In these distributions, Mesa is usually found in the official repositories. To install or upgrade:

sudo apt update && sudo apt upgrade -y
sudo apt install mesa-utils mesa-va-drivers mesa-vulkan-driv
st

If you want the Latest version from PPA (for Ubuntu and derivatives):

sudo add-apt-repository ppa:kisak/kisak-mesa
sudo apt update
sudo apt upgrade -y

In the case of those who are users of Arch Linux and derivatives, We install these with the following command:

sudo pacman -S mesa mesa-utils mesa-demos mesa-libgl lib32-mesa lib32-mesa-libgl

For whoever they are fedora users, you should know that updated packages are provided in their repositories and you just need to run:

sudo dnf install mesa-dri-drivers mesa-va-drivers mesa-vulkan-drivers

If you want more recent versions, you can use the Mesa Copr repository:

sudo dnf copr enable grigorig/mesa-stable
sudo dnf update

Finally, for those who are openSUSE users, you can install or update by typing:

sudo zypper in mesa