Windows 11 Virtual Machine Platform - WSL2 Boot Loop

[mackid1993]

On 7/28/2024 at 6:24 PM, wacko37 said:

Sadly this seems to be the case, as I'm having severe stability issues on the VM when gaming with this "custom" CPU passthrough method.

 

I'm not exactly sure why but after 20+ mins of solid gaming without any FPS drops / lagging the VM starts to lag hard, it never locks up totally but FPS drop to 10 FPS. Sometimes the VM recovers after 1min but it quickly drops to 10fps again, other times the FPS drop and then starts bouncing between 10 to 60fps ( have set a global limit of 60fps ) but it never fully recovers until a fully shutdown and reboot of the VM.

 

There seems to be no specific reason for it, as the VM was working absolutely perfectly with heavy loads before the FPS drops. Changing settings within the game has zero effect on this outcome or how the VM runs in general. I've mainly been using GTA5 to test but it doesn't matter the game at all.

 

I reverted back to the standard CPU passthrough mode applied by default in Unraid to test. I can see the moments where the VM starts to struggle but it always recovers quickly and FPS come back up, settings within the game most definitely have an effect on stability in this type of CPU passthrough.

 

It's almost as if certain features of the CPU are not being enabled correctly as @mackid1993 has pointed out, but I don't know how to go about proving that theory.

 

The only reason I'm using a custom CPU passthrough is because its the only thing that allows Roblox to be played within a VM as mentioned in my previous comment. Ive exhausted all other avenues to achieve this and I have no idea why the custom CPU passthrough allows Roblox to work but it does. Sadly that brings other no serious issues along with it.

 

Attached are both XMLs in .txt files

 

As always any advice or knowledge is much appreciated.

2024-07-20 - Windows 11 - Gaming VM - Custom CPU passthrough.txt 10.24 kB · 0 downloads 2024-07-27 - Windows 11 - Gaming VM - XML - Default CPU passthrough.txt 10.01 kB · 0 downloads

Just a suggestion. Buy an nvme drive, bind it to VFIO and pass it through over PCIe to your VM. Use a disk cloning tool such as Macrium Reflect to clone your vidsk to the nvme drive. Then boot baremetal into the nvme drive and play Roblox. Plug a monitor, mouse and keyboard into your server.

[wacko37]

5 hours ago, mackid1993 said:

Just a suggestion. Buy an nvme drive, bind it to VFIO and pass it through over PCIe to your VM. Use a disk cloning tool such as Macrium Reflect to clone your vidsk to the nvme drive. Then boot baremetal into the nvme drive and play Roblox. Plug a monitor, mouse and keyboard into your server.

Thanks for the time and reply as always.

 

I have really thought long and hard about doing a dual boot system to alleviate all the issues regarding a VM but decided against in the end because the servers primary purpose is to be a Server that's available 24/7, then 2nd to that are the dockers/containers also online 24/7, that's the only reason the system exists.

 

The VM was a added luxury and allows me to get the most out of that hardware thats running 24/7, but I'm sure you already fully understand my reasoning.

 

I have a dedicated/binded NVME drive to the VM, along with a GPU and NIC, lucky my 2080ti has a USB controller built-in so thats passthrough also. It's only really the CPU & Ram being shared.

 

It's like I'm so so close to having my perfect system/Gaming VM but yet so far away 😔 

 

Do you know what's the difference between the default CPU mode "Passthrough" and the "Custom" mode mentioned here in this thread?

 

Whatever that's doing it's appeasing Roblox for some reason.

 

 

Edited July 30 by wacko37
Spelling

[JonathanM]

7 hours ago, wacko37 said:

It's only really the CPU & Ram being shared.

Shared, yes, but also remember the VM "motherboard" is running in code on the host. Restrict the motherboard, hamstring the VM.

 

[wacko37]

7 hours ago, JonathanM said:

Shared, yes, but also remember the VM "motherboard" is running in code on the host. Restrict the motherboard, hamstring the VM.

 

True that, the glue that holds it all together how could I forget.

 

I'm stuck in a conundrum, with default CPU mode = passthrough my VM is stable and works a treat but Roblox crashes after 20sec without error.

 

On the other hand with CPU mode = custom Roblox works ok but my VM has delayed stability issues causing lagging.

 

It's thanks to the info on this thread and also from the last few comments from this GitHub thread (May 10th onwards) that helped me to get Roblox to actually load.

 

https://github.com/zhaodice/qemu-anti-detection/issues/56

 

For some reason changing the "Model=0" within the added <qemu:commandline> section to the XML allowed Roblox to function. From my limited understanding adding the <qemu:commandline> section to the XML seemed to override the default <CPU> section of the XML, this lead me to this thread and found that I didn't need the <qemu:commandline> section to achieve a working Roblox.

 

Sadly I have very limited understanding of what this is actually doing to allow Roblox to work. Surely there is some kind of tweak that can be applied when using the CPU mode "passthrough" that would appease Roblox.

 

Why can't my kids play something other than ROBLOX!!! 😭