This seems like the final technology in containing and categorizing different PC uses into different virtual machines, while still having good feel even in contained things. If set up right you can have a seamless experience tabbing between a host system and virtual system, and you can do whatever you can normally do in either one! Wanna use linux, but Discord hardly works and you like to play Halo too much to figure out how to dodge it's anti-linuxcheat system? Now you can switch to linux and just run a single script to pull up a fully gaming capable (near bare metal performance) windows system right inside a linux system. Idk about y'all but as far as cool technology to talk about in here goes... this definitely fits for me. I feel like if more people knew this was something you could do relatively easily (if you enjoy tinkering with your OS) with MOST consumer Nvidia cards (20 series and older), Linux would've already passed 5%. What do y'all think about it? The ability to, off a single consumer CPU and GPU, host several acceptable, mid-performance, cloud accessible (or just virtually separate, locally accessible) PCs?

In an effort to get a setup going where I can virtualize windows with ~native performance, so I can fully stay on linux for my actual OS, I've been looking into vGPU tools. Since I know (and have tested) that Hyper-V on Win10 can virtually share a GPU between host and guest, I assumed it must be doable on linux, and while that does seem to be the case, I'm having a lot of trouble making sense of the current state of things.

The biggest thing for me is GVM, which is a technology mentioned and linked in the setup guide... leading to a dead link at linux-gvm.org. Does anyone know where documentation is currently hosted for that? I find it difficult to dig through related repos that link back to the same site, and all the Kali tool links for the thing they call GVM.

If there's anyone around here more involved (or more knowledgeable in general) than me (not hard, probably most of y'all), maybe look into it if vGPU stuff interests you! Then come back here and let me know what I was missing cause I feel stupid trying to understand mdev and GVM vGPU differences.

That aside, based on open-iov's own guide having warnings to follow the other one, and said other one having some VERY unclear steps (Section 5.3.4 referring to previously made yaml edits when none were mentioned), I imagine that tool is not too actively maintained. Does anyone know where I might find some outline or guide to setting that system up from scratch?