It sounds like you’ve made significant progress in setting up VR with your Quest 3 using Hyper-V and the Meta/Oculus Link application, but you’re encountering issues at the final stage. Here are a few suggestions to help troubleshoot and possibly resolve the problems.
First, ensure the USB controller you are passing through to the VM is stable and fully supported. Sometimes, a dedicated PCIe USB card can provide better results than relying on the motherboard’s USB ports. Additionally, ensure all your drivers, including the GPU driver in the VM, are up to date. The same goes for the Meta/Oculus Link software and firmware on your Quest 3.
Regarding Hyper-V configuration, consider disabling Enhanced Session Mode if it is enabled to see if it improves the situation. If you’re running Hyper-V within another hypervisor, ensure that nested virtualization is enabled. Check the VM’s GPU settings to ensure that the GPU is correctly passed through and that there are no conflicts.
Network configuration is another important aspect. Sometimes, VR streaming over the network can be sensitive to latency and bandwidth. Ensure your network setup (both VM and host) is optimized for low latency and high bandwidth. For ALVR configuration, verify the SteamVR settings for the correct GPU and display configuration. The green screen in VR might indicate a problem with the video signal or encoding, so check ALVR settings and ensure compatibility with your GPU.
The BSOD with REFERENCE_BY_POINTER stop code often indicates a driver issue or a problem with system memory management. Ensure that all drivers, especially the GPU driver, are the latest versions. Consider running memory diagnostics to rule out memory issues.
Ensure that the guest VM has sufficient CPU and RAM allocated and that the GPU is correctly isolated for the VM, avoiding any resource conflicts. Lastly, check the logs from the Meta/Oculus Link application and any Hyper-V logs for more detailed error messages that could provide more insight into what’s going wrong.
If you’ve tried these steps and are still encountering issues, providing specific error messages or logs can help diagnose the problem further.
So essentially, with two Steam accounts and 2 copies of a game, you could use this to simulate the early 2000’s split screen experience on a TV as the monitor with only one PC and one GPU?
I’m still motivated to do the VGPU mod so I can do this in KVM without windows on bare metal (ew)
I installed an windows 24h2 preview build (Version 24H2 Build 26100.1591) on an external ssd and tried it again. The bluescreen didnt appear so far. i restarted steam vr multiple times and it didnt crash my host like before on 23H2. It only resulted into weird glitches where my system host explorer would freeze sometimes and my nvidia gpu driver going crazy and displaying wrong colors.
Unfortunately no games were are able to run. Virtual Desktop would show me only the desktop of the guest vm. i was able to interact with apps etc… but for anything related to steam vr it would either crash the virtual desktop service on my guest system or it would crash steam vr with this error ( Error: Not Initialized (109) (109)). Steam also complained multiple times that my headset wasn’t connected or my graphics drivers are not up to date. I wasn’t able to try ALVR or Meta Quest Link yet.
Im going to keep looking what I can do for the games and keep it updated here.
But regarding the bluescreen with REFERENCE_BY_POINTER stopcode you have to upgrade to 24h2. Seems to be an issue with the driver and it apperently was fixed in the WDDM 3.2 Version of the driver. And also make sure the host and the guest are on the same version and build.
Anyone have any luck fully completing this with an AMD 7900 XTX?
I am trying to go from a win11 Host to a Win10 1909 build and I am struggling to either pass my win11 drivers on, or I went and got the win10 drivers and passed those on.
Also I ran the PS scripts to add gpu partitioning to the target VM.
Both driver setups seem to not have the VM device mgr detect the 7900xtx.
This seemed to work on the a win11 host to new win10 iso, but not win11 host to win1909 build.
Hi, I am working on a Splitscreen Setup for my Gaming PC with a NVidia RTX 4090. I have setup 6 Windows11 HyperV-VMs, which all have an VMGPUAdapter configured. I can run a game on 4 VMs sequently with no issues. When I try to start the game on the 5th VM it will only open only ~10% of the time. Never on instance 6. But not only that, also everything in Windows has weird issues, even cmd is throwing errors when I try just to open the command line. Weirdly, when I manage to start them at the same time, there is a chance that all games open. And when they do, they run just fine with 60fps, so it’s not that the 4090 couldn’t handle this.
Also tried increasing or decreasing the max vram and min vram etc. settings of the adapter, but that doesn’t seem to have any impact.
Hello, funk192, your post is what I was looking for so many days or weeks and I’d like to know how to install Nvidia driver directly to the Hyper V vm.
How do you spoof VM? Should I copy this " Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\PCI"?
Also which drivers ( there are a few drivers (.inf) files in nvidia folder) need to be copied into hostDriverStore?
how to restart both NVContainerLocalSystem and NVDisplay.ContainerlocalSystem services? I am not sure they are excutable.
Could you explain the whole process step by step, please? I will really appreciate it.
Device manager shows my graphic card ID details of this following: PCI\VEN_10DE&DEV_2C05&SUBSYS_53101462&REV_A1
PCI\VEN_10DE&DEV_2C05&SUBSYS_53101462
PCI\VEN_10DE&DEV_2C05&CC_030000
PCI\VEN_10DE&DEV_2C05&CC_0300
Which one is device ID among these numbers? Thanks in advance