[TUTORIAL] Windows 11 VM for gaming setup guide

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.
 
What is with the latency / remote video timings and input lag? I can't believe that FPS is playable...
 
Jay. said:
What is with the latency / remote video timings and input lag? I can't believe that FPS is playable...
Click to expand...
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.
 
  • Like
Reactions: Jay.
tomppa said:
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.
Click to expand...
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.
 
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.
 
Thanks for this tutorial. Works great (I do not use anti cheat features so I cannot comment on that). I wondered if things could get easier to install with the recent resource mapping option ? (from within datacenter)
 
tomppa said:
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.
Click to expand...
Vanguard requires a pretty nasty ring-0 privilege on Windows, pretty difficult to trick it.

However I've heard whispers that they do not have the same level of access on MacOS. If I were you, I'd try a MacOS VM. That itself is not an easy journey. If you try this and succeed I'd love to hear about it, I'd love to play a few ARAMS but hoarding data is more important to meat the moment
:cool:
 
  • Like
Reactions: wassupluke
I'm a little lost, if anyone has any ideas. I followed the steps as best I could but my Windows 10 (I know, not 11) VM still won't boot. It's getting stuck pre-boot in proxmox:

Code: 
error writing '1' to '/sys/bus/pci/devices/0000:01:00.0/reset': Inappropriate ioctl for device
failed to reset PCI device '0000:01:00.0', but trying to continue as not all devices need a reset
swtpm_setup: Not overwriting existing state file.
kvm: type=1,vendor=American Megatrends Inc.,version=P3.10,date=10/24/2018: Could not open 'type=1,vendor=American Megatrends Inc.,version=P3.10,date=10/24/2018': No such file or directory
stopping swtpm instance (pid 6775) due to QEMU startup error
TASK ERROR: start failed: QEMU exited with code 1

My args:
Code: 
args: -cpu host,-hypervisor,kvm=off,-smbios type=1,vendor="American Megatrends Inc.",version=P3.10,date="10/24/2018"

From my dmidecode:

Code: 
Handle 0x0000, DMI type 0, 26 bytes
BIOS Information
        Vendor: American Megatrends Inc.
        Version: P3.10
        Release Date: 10/24/2018

This post implies that the PCI errors may not be a problem: https://forum.proxmox.com/threads/w...ckages-broke-my-pci-passthrough.156848/page-3

and I changed the -smbios parameter to type 1 as that is what's reflected in the web GUI for proxmox ("SMBIOS settings (type 1)") under the options tab for the VM.

Do I need to generate a bios file or something before I can boot? I'm not sure how to proceed with troubleshooting this.
 
blamante said:
It's fixed with
echo 1 > /sys/module/kvm/parameters/ignore_msrs
Click to expand...
Actually it is "echo Y" but "echo 1" might work too. (edited for clarification) If you look at all the other parameters in that directory they are either Y or N. So I just went with Y. It's possible that 1 or 0 will work for Y or N.
 
Last edited:
You must log in or register to reply here.
Top Bottom