Unable to capture a monitor using a virtual monitor in proxmox vm windows 11,10 with sr-iov

[HolyCom]

First, I referred to "https://www.amyuni.com/forum/viewtopic.php?t=3030 " for creating a virtual monitor.

First, we created several vgpu using sr-iov technology and passed one of them to Windows 10 or Windows 11. As a result, normal hardware encoding was possible in handbrake encoding programs and other encoding programs. This works fine with the latest drivers as well. However, "parsec" and "sunshine", which are remote control programs that capture and send screens, were not possible in the latest version of drivers. Previous versions of "https://www.intel.co.kr/content/www/kr/ko/download/741626/780560/intel-arc-pro-graphics-windows.html " drivers were only able to transmit to hardware encoding through virtual monitors normally.
Initially, I tested it only on Windows 11 and determined that it might be a problem with Windows 11, so I installed and set up a new Windows 10 vm, but the same problem occurred. Installing the older version driver also fixed the issue. This impairs the user experience.

Attached is the proxmox setup window ssu log below. Until now, the only program that was sent through hardware encoding after screen capture was "rustdesk".

[Alberto_R_Intel]

HolyCom, Thank you for posting in the Intel® Communities Support.

We will be more than glad to assist you with this matter. 

Based on the information shown in the SSU document, the graphics driver version currently installed on your computer is 31.0.101.4648. For this scenario and in order to try to fix this problem, we just wanted to let you know that there is a newer graphics driver version available on our website, which is 31.0.101.4887. Please try a clean installation of that driver following the instructions in the links below:

https://www.intel.com/content/www/us/en/download/785597/intel-arc-iris-xe-graphics-windows.html?wapkw=arc

https://www.intel.com/content/www/us/en/support/articles/000057389/graphics.html

We also recommend to get in contact directly with the manufacturer of the device to make sure that the latest BIOS version is currently installed on your machine or to gather the instructions on how to update it.

For some reason, the model of the board is not showing in the SSU report. If the issue remains after trying the suggestions provided above, could you please provide the model of the motherboard?

Any questions, please let me know.

Regards,

Albert R.

Intel Customer Support Technician

[HolyCom]

Of course, it's running ssu in a vm window environment, so there won't be any motherboard information.
I'll give you the motherboard information for the host computer where "proxmox" is installed.
"https://kr.msi.com/Motherboard/MAG-B760M-MORTAR"

In addition, I tested it after installing the driver of the "31.0.101.4887" version, but I could not encode the hardware after capturing the screen. It's been done in the old version, but not in the latest version, so I think it's a clear driver issue.
In addition, I will attach the ssu log after the latest driver installation.

To sum up, it's not that hardware encoding itself is impossible. The handbrake lamp encoding program operates normally. This is a problem with hardware encoding after screen capture of remote control programs. Also, this is not a problem with remote control programs.

[Alberto_R_Intel]

HolyCom, Thank you very much for confirming that information and providing an updated SSU report.

We are sorry to hear the issue remains after installing Intel® graphics driver version 31.0.101.4887.

Based on that, I will do further research on this matter to try to find a possible solution for this scenario. As soon as I get any updates, I will post all the details on this thread.

Regards,

Albert R.

Intel Customer Support Technician

[Alberto_R_Intel]

Hello HolyCom, I just received an update on this matter.

While we are still working on this topic, we just wanted to confirm, step by step what was done, or which page with the manual was used? 

This is in order for us to gather the exact instructions you followed so, if possible, we can try to replicate the issue in our Intel® lab.

Regards,

Albert R.

Intel Customer Support Technician

[HolyCom]

https://github.com/strongtz/i915-sriov-dkms?ref=michaels-tinkerings
We followed the instructions above to activate sr-iov in proxmox.

[Alberto_R_Intel]

HolyCom, Thank you very much for your reply.

We will now continue working on this scenario, based on the information shown in the link you shared, and provide a response as soon as possible.

Regards,

Albert R.

Intel Customer Support Technician

[HolyCom]

In addition, the latest kernel, "6.2.16-18-pve," has a problem. You should try versions below "6.2.16-15-pve".

[Alberto_R_Intel]

Hello HolyCom, Thank you very much for sharing those details.

We just wanted to let you know that we are currently investigating this topic. As soon as I get any updates, I will post all the information on this thread.

We apologize for any inconvenience.

Regards,

Albert R.

Intel Customer Support Technician

[HolyCom]

It's been about a month. Is there any progress?

[Alberto_R_Intel]

Hello HolyCom, Thank you very much for your patience. I just received an update on this matter.

After reviewing the case we just wanted to let you know that we did a test trying to replicate the issue and there were no issues in our results.

Steps:

-vGPU configuration: BAR enabled, PCI express enabled, Primary GPU enabled, All functions disabled.

If all function options are enabled then all vGPUs will be disabled and only "physical" one will be available for full passthrough.

-Installed Parsec (with/without virtual display driver) and TightVNC for remote connection

 -Apps which should use iGPU must be set in Windows graphics settings.

-Standard RDP connection works always and create it's own temporary GPU device.

-VNC can connect to VM but not when only iGPU is present in VM. Having virtual display driver from Amyuni installed and enabled one virtual screen the connection as possible using VNC.

-When vGPU is the only display device in system, remote connection can be established only via RDP.

 So, in this case, it is important to mention i915 driver is supported by Intel in Ubuntu, the usage in other systems is best effort. Ubuntu-based distros may behave similarly or not to Ubuntu depending on the level of modifications. There are too many Linux distros to have all of them check and test solutions. Based on that, we recommend to verify the details shown in the following document:

https://dgpu-docs.intel.com/driver/client/virtualized.html

And also, to check with the Linux distro directly for further technical assistance on this matter:

https://www.intel.com/content/www/us/en/support/topics/linux-osv.html

Regards,

Albert R.

Intel Customer Support Technician

[HolyCom]

Do you mean that you installed parsec and tigervnc on Windows at the same time? And please explain how you set up the Windows graphics.

[HolyCom]

Just in case, even if you set the window graphics (770 uhd) on parsec, parsec still hasn't been able to remotely control it. I don't know why it's possible with older versions of drivers and not with newer versions.

[HolyCom]

And also, if you set that setting in Proxmox, you need to set the vm display setting to none to work properly. If you don't set it to none and set it to a different setting, it will work like parsec. But in this case, it doesn't work as hardware encoding, it works as software encoding. You don't use gpu.

[Alberto_R_Intel]

HolyCom, Thank you very much for your answer.

I will confirm those details, gather the information you are requesting, and provide a response as soon as possible.

Regards,

Albert R.

Intel Customer Support Technician

[Alberto_R_Intel]

Hello HolyCom, I just received an update on this matter.

1. Yes, Parsec and TightVNC server can work on the same machine without any problems. There is no reason why they couldn't coexist.
2. All proxmox config and VM config was according to manual (in VM, "all functions" option must be disabled)

• VM setup according to manual:
  • configure Vm without PCIe device (vGPU)
  • Install Windows, configure remote connection, power off
  • Add vGPU, set previous display device to none
  • run VM and connect via RDP
  • Install Intel drivers

Parsec wasn't working every time as it should be, VNC was better, RDP was best.

This driver is not working properly at 100% with Proxmox when we're talking about vGPU scenario, it might be better under Ubuntu+KVM.

Under Proxmox this vGPU solution (as tested) works but without video output - only "computing" power. That's why that other virtual display driver was needed.

Regards,

Albert R.

Intel Customer Support Technician

[HolyCom]

In the case of rdp, it supports its own display. After all, there seems to be no way with sr-iv technology, which can't plug in hdmi dummy plugs after the driver update. So, does Intel plan to support its own virtual display when there is no display connection?

[Alberto_R_Intel]

Hello HolyCom, Thank you very much for your response.

I will confirm those details and share the updates as soon as they become available.

Regards,

Albert R.

Intel Customer Support Technician

[Alberto_R_Intel]

Hello HolyCom, I just received an update on this matter.

In reference to this topic, if there will be any changes, then all updates should be in "readme" or release notes in the main GitHub repo.

As an option, in order to gather additional details on this subject, please visit our Intel® Resource and Documentation Center website where you will find further aspects about this topic:

https://www.intel.com/content/www/us/en/resources-documentation/developer.html

Regards,

Albert R.

Intel Customer Support Technician