Search results

Hi Clement, At least a small progress is done. I need some more info about your setup and would ask for another test: 1. Can you run the same test but not between VM but the physical PC (with the same AMD) and connect Nvidia HOST to it? We need to make sure the problem is related with the VM...

Hi Clement We have successfully run an AMD RX5700 on the Hyper-V. It works and HEVC is streamed using GPU acceleration in Remotly on the VM. It looks like recent Intel GPUs work and AMD RX5xxx (and newer) too.

RX560/580 does not fully support GPU virtualization... We will check with RX6xxx tomorrow.

UPDATE: AMD RX560 works after disabling "Enhanced Session" and checkpoints. But AMD AMF video encoders fail. Only SW encoding works.

It looks like it also crashes on AMD RX560. This time only the VM not the entire PC.

We have just uploaded a new update that includes important improvements for Hyper-V VMs, multi-account systems as well as some other improvements and fixes (special thanks to user ClémentRED who spent his time during the weekend on helping us with Hyper-V issues): - Temporary workaround for...

Version 1.11.2 is now available in the download section.

The new v1.11.2 version is almost ready. You will now see this message during startup:

Hi Clement, Yes, please write/contact Nvidia. We will also contact them but from our experience they respond faster when they get feedback from multiple sources. They'll also see this crash in their logs from Microsoft when BSOD crash occurs but God knows how long it will take for them to...

I have managed to start Remotly without crash on the Hyper-V VM running with Nvidia. To do so you need to rename this file (on the VMs file system): C:\Windows\SysWOW64\nvencodeapi.dll to another name for example: C:\Windows\SysWOW64\nvencodeapi.dll_ This way Remotly won't find it and will not...

I give up :( The crash is in nvencodeapi.dll. The same dll is used in non-VM (physical) system and it works fine there. If AMD will work then this is Nvidia's bug. BTW All Nvidia HW video decoders work fine from the Hyper-V VM.

I know more now. As expected the crash happens during querying GPU encoder capabilities. It might be something with HDR.

I will start by disabling GPU initialization of various modules. I hope I can find what is causing this in less than 2 hours ;/ Anyway, I think this should be reported to Nvidia. Imagine a server with shared GPUs in a datacenter and someone runs this... This is surely a bug in Nvidia drivers...

Ok have the same problem on RTX 2080. The entire PC crashes (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED).

Hi Clement, I'm still setting up Hyper-V on a dual Nvidia RTX system. In the meantime please find how I have made it work on the Intel GPU system: 1. Install git if you do not have it 2. Clone the Easy-GPU-PV repository - run PowerShell with admin rights, go to the directory where you want...

Theres is another one for GPU memory. I will paste it here soon.

I'm wondering why does parsec need this virtual driver installed on a VM... These drivers have poor performance. They must use it for setting up virtual displays I guess. I'm sure we will fix these problems soon Clement. Thanks again for your cooperation regarding this! I will later write a...

Did you disable "parsec virtual display driver" or uninstall it completly? (Is it still on the list)

Did you use 2 Easy-GPU-PV scripts? One was for installing drivers and the other one for GPU memory? I will send how I used the scripts soon. I'm setting up Hyper-V on Nvidia and AMD now.

Funny thing... It only works properly when running Remotly with admin rights :) BTW do you have the "Enhanced session" enabled? Remotly works ok in current 1.11.1 version but only when "Enhanced session" is disabled. In the new 1.11.2 version it works with and without "Enhanced session".