Yeah I'm pretty sure with some simple virtual network bridges and routing rules a 4-to-6 converter is plenty possible without touching the actual processes.
I was just expecting it to be something built into chrome, similar to how drivers need to be signed to run in windows, they'd force you to use browsers Signed By Google to be verifiably compliant with the DRM. It seems like the easiest option for them and the most well understood since it's been used for drivers for so long
Based, if I can, I will edit the original link to use piped
Well at least for Nvidia, vGPU is a fully Enterprise tech for accomplishing splitting a GPU between a host and VMs. It also just so happens to work on all 20> series cards if you patch the driver :}
You can not just pass through, but share any1 gpu you like using HyperV. Yes it's Win10Pro, but there are pleeeeenty of ways to get it enabled/installed/supported on Home as well. Though if you have an Nvidia card 20 series or older, and you're willing to dive into linux as a dual boot, I'd say qemu/virt-manager is a pretty mainstream VM solution, and vGPU is also a good tech for the same purpose.
1 I'm not actually sure what the limits on hyperv are but it seems fairly robust. Don't quote me on it lol
Huh, neat. Regardless, I think google will find a way to sell it or they wouldn't be invested in it so much, but point taken. I just saw a lot of people commenting on other places about how this is hopeless and there's no way to protest and wanted to give a solid example of how it could be done effectively.
Wait were they seriously looking to implement it at a FIRMWARE level? jesus that's just stupid.
Specifically to set up a system like the one I've finally got. A hypervisor that retains its own display capabilities, while being able to share the full GPU (though only set portions of VRAM) freely and on demand, with a VM. We can shit on Nvidia all we'd like for a lot of stuff, but vGPU works really well, even on cards it isn't meant to support LOL
Between the discord devs outright refusing to do any kind of sound capture for linux screen sharing for several years, many updates requiring you to manually download and install a fresh tarball instead of being automatically applied like on windows, and refusal to maintain any kind of package on most repositories, I'd say it doesn't properly support linux. I do like Nobara's version of it, whatever they've done (I haven't looked much into it but it definitely seems custom to Nobara, or at least Red hat) though.
And speaking purely from personal experience with no real way to verify statistically (so take this with a rather large grain of salt), there are a LOT of CS or CE major types that would love to switch to it, but will be faced with random tools that they need like microchip studio, or some particular CAD software, just not working at all. For those that I've talked with at any length, if they could spin up a VM that effectively fully works as if it's bare metal, including proper display out that matches the monitor, whenever they need those few specific things, they would switch. They may not be many compared to 100% of global internet users, but they could certainly make up for 2%.
That said I mostly agree that devices like the steam deck are where linux is gonna grow, I just think that it would be going faster if more devs were able to daily drive it and care more about it, instead of having to be stuck reliant on Windows
That's where you'd be wrong! I'm running it on my 1080ti right now. It can be hacked into working on just about any Nvidia card that's recent enough to want to use it. A bit of a community has ended up growing around a group that makes patches for the official vGPU drivers, along with merge scripts, to give the hypervisor the ability to retain regular function (accelerated display out through the DP/HDMIs), while also fooling the vGPU part of the driver into thinking the random consumer card is supported. Unfortunately locked down on 30 series and newer :(, but it's still a VERY cool use for a card like the 1080ti that has become VERY cheap
I could go into the conspiratorial 4D chess I'm sure google is playing, but let me ask this instead: Does you bank not have any captchas, anywhere in the flow of accessing/using their website? Cause if they do, I hope you know google is absolutely going to advertise DRM requirements as the best tech for fighting bot traffic. Even if Google wasn't doing anything like offering cheap training to their standards to influence the future of the cybersecurity space, that would be PLENTY to get a looooot of big corporations, including banks, to use it.
Close, but that's not what I mean. I mean SEAMLESS sharing, not playing tennis with it. Is it really so poorly known? Should I write up a little introduction to the parts of it that I'm familiar with?
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?
They want to go back to the days of websites requiring internet explorer... just this time with their browser. Even though getting away from that culture is most of the reason people ever switched to chrome. I will say though, just using firefox for everything you can isn't enough of a protest. If this goes the way Google (Alphabet I guess) wants it to, you bank will require you to use a browser with DRM. You will be forced to use a browser whose source code you can't verify as secure, to access your bank. And that is where the protest lines need to be drawn. If your bank does that? Send your message. Close the account. Take back your money. Now I'd personally do this for everything possible, but that would be a looooot of time spent getting very little across to companies that don't care if you visit their site. Taking money from banks though? Yeah it might be a whole process where you gotta request it, verify in person, wait a week to get the cash, and THEN close it, but so what? A couple hours of doing stuff and then a week of business as usual before a couple more hours opening a new bank account. That's more than worth doing to send a REAL message.
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?
Going to school for hardware, but spending as much time as possible on system level software/firmware. It's lots of fun, really. Assembly is just like solving puzzles.