this post was submitted on 18 Jul 2025
85 points (97.8% liked)
Programming
21924 readers
610 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The other points have been answered, so I'll try and give a surface view of Magma. It's basically an abstraction layer for virtual GPU drivers used in VMs. Currently, you need specific implementations to handle all of the pathways between different types of VM guests and hosts, which gets complicated fast, and duplicates a lot of work. The idea is the Magma abstracts this away, and so host and guest GPU drivers only need to interface with Magma. Which means you can swap out different host OSes/GPU drivers and different guest OSes and GPU drivers, and as long as they interface with Magma, they should "just work".
Of course, whether it will work out that way in practice remains to be seen. I think Google is using it internally but it's not in Mesa yet, so it may not even roll out widely. You can follow the MR if you want more detail or to see its progress.
If you're wondering why Google is implementing this it appears to be for Fuschia and Android, and compatibility between those two and with desktop Linux, with Windows support also supported as an additional value add. Chromebooks in particular should benefit from this, since ChromeOS is being retired I believe.
And as an aside, unlike some of the traditional GPU implementations you'd find in VMs, these are or will be pretty much just the normal graphics driver that you'd use on the host. They are generally called "native contexts" and have been implemented for AMD and Intel at the least, but only on non-Windows systems for now. These implementations alone, once they are widely supported, should result in near native GPU performance in VMs, without having to use GPU passthrough (I.e. passing through a physical GPU to the VM guest). So even without Magma there's some promising stuff happening, albeit mainly on the Linux host -> Linux guest pathway.
Thanks, this is the answer to the question I was just asking! (What is Magma trying to solve).
Can you dive a little deeper in how Magma is solving this? Don't VMs have a virtual GPU with a driver for that GPU in the guest that, I imagine, forwards the graphics instructions and routines to the driver on the host? (possibly even translating to OpenGL or VK that then is handled by Mesa?). Where in that does Magma come in? My guess is that magma sits in the guest as the graphics driver and on the host before Mesa, but I know little about virtualisation outside of containers.
Also, what are these "native contexts" you speak of? Are they like the virtualisation extensions on CPUs that VMs can directly use?
Anti Commercial-AI license
I'm not really an expert, but I'll try and answer your questions one by one.
Yes, this is what VirGL (OGL) and Venus (Vulkan) do. The latter works pretty well because Vulkan is more low level and better represents the underlying hardware so there is less of a performance overhead. However, this does mean you need to translate all APIs one by one, not just OGL and Vulkan, but also hardware decoding and encoding of videos, and compute, so it's a fair amount of work.
Native contexts, in contrast, are basically the "real" host driver used in the guest, and they essentially pass through everything 1:1 to the host driver where the actual work is carried out. They aren't really like virtualisation extensions as the hardware doesn't need to support it AFAICT, just the drivers on both the host and the guest. There's a presentation and slides on native contexts vs virgl/venus which may be helpful.
To be honest, I don't fully understand the details either, but your interpretation seems more or less correct. From looking at the diagram on the MR it seems that it's a layer between the userspace graphics driver and the native context (virtgpu) layer on the guest side, which in turn communicates with another Magma layer on the host, and finally passes data to the host GPU driver, which may be Mesa but could also be other drivers as long as they implement Magma.
The broader idea is to abstract implementation details, so applications and userspace drivers don't need to know the native context implementation details (other than interfacing with Magma). And the native context layer doesn't need to know which host gpu driver is being used, it just needs to interface with Magma.