[TUTORIAL] Windows 11 VM for gaming setup guide
- Thread starter MichaelBernasconi
- Start date
I just encountered the first real problem: Riot Vanguard does not work. The service simply won't start without much feedback.
Perhaps it has something to do with it not being able to edit the Secure Boot? I'd be glad to hear if anyone has overcome this.
Perhaps it has something to do with it not being able to edit the Secure Boot? I'd be glad to hear if anyone has overcome this.
I haven't objectively measured it, but it's negligible for me. Noticeable, maybe, but not problematic. I also have a lot of VMs and containers running in the background.
The only thing I have to figure out is how to get rid of weird freezes and stutters. They weren't there when I first set it up (system was practically as responsive as bare metal), but with the heavier load (or maybe Windows shenanigans) there are some small issues.
How do you connect to the VM? Via RDP Session over Network? To test it, I ran a YouTube video in an RDP session and when I moved the slider for the timeline under the video, I got a noticeable delay. I also have a delay in my 3D CAD application and I think that would also be the case in games.
Excellent tutorial!
In case you have two GPUs sharing the same driver, one for host and one for VM, by blacklisting the driver the host GPU will not work either, the "driverctl" tool can be used to override the GPU driver to vfio-pci.
[1]: https://www.heiko-sieger.info/blacklisting-graphics-driver/#Using_the_driver_override_feature
[2]: https://gitlab.com/driverctl/driverctl
In case you have two GPUs sharing the same driver, one for host and one for VM, by blacklisting the driver the host GPU will not work either, the "driverctl" tool can be used to override the GPU driver to vfio-pci.
[1]: https://www.heiko-sieger.info/blacklisting-graphics-driver/#Using_the_driver_override_feature
[2]: https://gitlab.com/driverctl/driverctl
Just wanting to chime in with issues/solutions that I ran into while going through this process.
My hardware is a Supermicro SV-4028GR-TRT with 2x Xeon E5-2699 v3 installed.
When booting to Windows I immediately encountered a BSOD (unfortunately, I didn't get the exact error code but it IIRC it mentioned the system and something not being supported). After reading through all of the posts before now I didn't find anything that I wanted to try out as they seemed to mess with arguments being passed or for AMD instead of Intel processors and instead opted for removing the Windows ISO from the Hardware section of the VM and trying out passing through a physical USB with the Windows installer on it and BAM, worked perfectly!
I'm not sure what would cause this issue (maybe drivers?) but thought it would be useful to mention here in case anyone ran into similar BSOD issues as this is an easy fix to try.
My hardware is a Supermicro SV-4028GR-TRT with 2x Xeon E5-2699 v3 installed.
When booting to Windows I immediately encountered a BSOD (unfortunately, I didn't get the exact error code but it IIRC it mentioned the system and something not being supported). After reading through all of the posts before now I didn't find anything that I wanted to try out as they seemed to mess with arguments being passed or for AMD instead of Intel processors and instead opted for removing the Windows ISO from the Hardware section of the VM and trying out passing through a physical USB with the Windows installer on it and BAM, worked perfectly!
I'm not sure what would cause this issue (maybe drivers?) but thought it would be useful to mention here in case anyone ran into similar BSOD issues as this is an easy fix to try.