US only I suspect, and likely to be gutted by the Trump administration.

I’m not really an expert, but I’ll try and answer your questions one by one.

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?

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.

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.

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.

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.

I’m guessing it’s the AI agent stuff. Which at the moment is literally just automating browsing through a website.

Apparently there will be APIs to do this in the future. Ironically, AI wouldn’t even be needed for that to be useful.

mpv supports Dolby vision (along with the Jellyfin clients that depend on it), but if you mean with streaming services, that’s unlikely to happen due to DRM.

Youtube varies from genuinely good content, to generic filler, to complete and utter trash, and there is much of the latter two because it’s not curated by anyone (other than by algorithms).

Try “We Own This City” from David Simon, if you want a documentary on the police that isn’t propaganda.

I’m almost at the point where all of my connections are IPv6, but still hampered by my mobile provider (ironically, since IPv6 was generally adopted earlier on mobile in many countries).

Clean living in his view just means focusing on “natural” things. Which means swimming and drinking shit water is safe, but anything “artificial” is dangerous. So he’s certainly not going to care about pathogens in the food supply, because he doesn’t believe they are dangerous.

These are quirky in terms of plot but not so much in terms of gameplay (at least your modern examples). That’s fine to a point but I’d like to see a bit more variety.

I thought it was clear from context I was talking about X.

Most of those are lesser evils compared to X, and that’s probably the best you can hope for. And Bluesky is the obvious alternative lesser evil choice if you want a like for like replacement and aren’t open to Mastodon.

If you’re technically inclined, self-host navidrome or jellyfin.

If you just want music and don’t care about the streaming part, bandcamp (although it does have some basic streaming I believe.

If you want streaming and aren’t technically inclined, Tidal.

I get where you’re coming from, but it’s not like there aren’t multiple obvious alternatives (and not just on the fediverse). And someone being clued in enough to boycott Spotify should have no trouble finding those alternatives. Additionally, the platform being owned by an outright Nazi should give even the most out of touch people pause.

But agreed that people could stand to be a bit more tactful about it and not immediately go on the attack.

Not to mention giving 100s of millions of dollars to fund Joe Rogan and his extreme right-wing propaganda.