It'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.
- 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.