3 ms·
and why anyone would allow windows to touch their hardware directly ?! it belongs ( at best ) inside a QEMU/KVM vm.
by slipwalker 4y ago
and why anyone would allow windows to touch their hardware directly ?! it belongs ( at best ) inside a QEMU/KVM vm.
- seanw444 4y agoEven if you use it for gaming. Get a cheap GPU as a display driver, slap it in an extra PCIe slot, let Linux use that card as a simple display driver, and then pass through your beefy GPU. If you have it configured right, the performance difference will be nearly on par with bare metal. It actually baffles me how good QEMU/KVM is.
- ManlyBread 4y ago>If you have it configured right Yeah, no, I'd like to unwind and have fun instead of messing around with config files and drivers
- seanw444 4y agoIt's surprisingly straightforward, especially with the Arch Wiki. The main two things are: - Figuring out input switching. You don't want your inputs locked into the guest until you shut the guest down. - CPU pinning. Otherwise your performance will get hammered with your L3 cache getting trampled by the host. Do it once, and it's way more straightforward from then on than dual booting. Especially because then you can use virtual disks that only take as much disk space as you want to use, and they're easily resizable via NBD. Rather than allocating a huge static partition on your drive. And then Microsoft and all the blackbox code your games run don't have the capability of spying on the rest of your storage by default.
- ManlyBread 4y agoI appreciate the answer but I want absolutely nothing to do with configuring anything when I sit down to play a game.