search

jamesstringerparsec / Easy-GPU-PV

A Project dedicated to making GPU Partitioning on Windows easier!
4.21k stars 422 forks source link

Limits of GPU-P and Hyper-V #168

Open kallell opened 2 years ago

kallell commented 2 years ago

Not so much an observation but rather a conversation topic.

It seems there starts to be VM issues post 4 vms - regardless of the resource allocation - gpu/cpu/memory/HDD. This seems to be bot the case with windows 11 and windows 10. Host is windows 11.

I was up to 6 vms, running games to test out the limits. Initially only needing to allocate 8% gpu to each. Monitoring both guest and host - host did not go past 50% utilization in any means. Guests (4 gb ram, 75 gb hdd, 8% gpu, 4 cores), were only at 50-75% utilization, most being ram.

However, after a few days of this, I can't successfully launch more than 4 of the 6 (doesn't matter which ones). I have gone from 5% - 50% gpu utilization for each, but it doesn't seem to matter. Before even launching any games or pushing the GPU, the partitioning doesn't even seem to work (via device manager, it'll end up with a ! point). Typically, this would mean a driver issue, but if another vm is shut down in place and is rebooted, this ! on the machine goes away. More or less, it seems like it's getting limited for resource allocation to the GPU.

Additionally, some windows settings menu close instantly, and there is errors trying to click shortcuts or apps "File system error (-1073741819)". Again, this doesn't always seem to happen, only when using >4 VMS.

My computer is on the high-end, so I have more than enough to utilize this setup:

Asus rog strix rtx 3090 64 GB Crucial Ballistix 3600 MHz DDR4 DRAM SAMSUNG 980 PRO SSD 1TB PCIe 4.0 NVMe Gen 4 Gaming M.2 AMD 5950x CPU

Curious as to if anyone has had any other issues or have any ideas of what I could adjust/test/tweak.

Kodikuu commented 2 years ago

GPU-PV is not the most mature or user-friendly feature of Windows. Issues are to be expected. Just for reference, that filesystem error is STATUS_ACCESS_VIOLATION

kallell commented 2 years ago

GPU-PV is not the most mature or user-friendly feature of Windows. Issues are to be expected. Just for reference, that filesystem error is STATUS_ACCESS_VIOLATION

Really appreciate the reply, thank you. Any thoughts as to why I get limited to 4 VMs after a certain point? There has to be some logic to the issue.

xmattehx commented 2 years ago

I'm curious of this potential limitation also. I'm currently running into an issue where I can deploy 4-5 VM's through the script, however I can only Parsec (Teams) into a MAX of 3 VM's concurrently, upon connecting to the 4th via Parsec I get a -15000 error.

jamesstringerparsec commented 2 years ago

NVIDIA consumer GPUs support a maximum of 3 simultaneous encode sessions.

On Mon, Jun 13, 2022 at 2:09 PM Matthew @.***> wrote:

I'm curious of this potential limitation also. I'm currently running into an issue where I can deploy 4-5 VM's through the script, however I can only Parsec (Teams) into a MAX of 3 VM's concurrently, upon connecting to the 4th via Parsec I get a -15000 error.

— Reply to this email directly, view it on GitHub https://github.com/jamesstringerparsec/Easy-GPU-PV/issues/168#issuecomment-1154442049, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJGBUNRTL4OPA24CI2ALZMLVO6PSFANCNFSM5WDL6PYA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

kallell commented 2 years ago

Thanks for the info James. Found this - might be worth testing the patch to increase. https://github.com/keylase/nvidia-patch/blob/master/win/README.md

xmattehx commented 2 years ago

Thanks for the info James. Found this - might be worth testing the patch to increase. https://github.com/keylase/nvidia-patch/blob/master/win/README.md

I tried this in my setup, I was able to get 4 Parsec streams going...on the 5th I got VDD issues within Parsec.

kallell commented 2 years ago

The really odd thing is multiple times now, starting from scratch I can get 6 to run fine. Over time it just deteriorates and then eventually is capped out on 4 vms that actually function.

Black-Seraph commented 2 years ago

Keep in mind that hw-accelerated encoding tools count towards the encode session limit, so if your host system was doing other encoding-related work this might have contributed to your sporadic up & down in working VMs.

ante1377 commented 1 year ago

Anyone running a few vm's and at the same time run on the host machine itself and experience that the host sometimes completely freeze the graphics? (reboot all that "works"). Haven't had much luck trying to troubleshoot this but wondering if anyone else experience similar issues?

kallell commented 1 year ago

Anyone running a few vm's and at the same time run on the host machine itself and experience that the host sometimes completely freeze the graphics? (reboot all that "works"). Haven't had much luck trying to troubleshoot this but wondering if anyone else experience similar issues?

Yep. this was a common issue.

yasz commented 1 year ago

how about amd?

ante1377 commented 1 year ago

No idea , just to add you can unplug the screen cable from the GPU and back in again and screen comes back so no need to restart. No clue what really happens but better action then reboot 🤣

On Tue, Mar 21, 2023, 16:53 yasz @.***> wrote:

how about amd?

— Reply to this email directly, view it on GitHub https://github.com/jamesstringerparsec/Easy-GPU-PV/issues/168#issuecomment-1478089785, or unsubscribe https://github.com/notifications/unsubscribe-auth/AT27YDSDU4DCPBGFVQA3QUTW5HFG7ANCNFSM5WDL6PYA . You are receiving this because you commented.Message ID: @.***>

yasz commented 1 year ago

hope that AMD new GPU rx7900xt can support more than 10 vms sessions!