Well, not being able to leave well enough alone, I took another poke through the BIOS settings, and adjusted the PCIe slot from gen 5 to gen 4, and changed the PCIe power settings to “performance”, and at least for the moment, we’re up and running. I’ll see if it’s stable with multiple running…
the aer output seems like extreme pcie bus noise. riser cable in the mix here?
No riser cable. MS-A2, B50 directly installed into the PCIe slot (no shell on the case with the height of the card right now). The change to PCIe 4.0 may have made the difference in signaling with those errors.
Edit: May be worth noting the card doesn’t sit perfectly flat in the MS-A2 with the foam spacers that Minisforum is using and the backplate on the B50. I may look at removing those foam spacers.
Alright - a bit more poking and testing. Still using the Proxmox 6.17 kernel, and with the change to PCIe 4.0 I’m up and stable, but similar to PatrLind I’m getting horrible RDP performance (seems to be stuck at 9FPS, per Intel’s software).
I did run Heaven, and it’s showing between 60-120 FPS depending on the scene with DX11, but that doesn’t affect the rest of the session window’s performance. I did try to tweak the max framerate for RDP via registry key, but that actually made the issue WORSE, with notable cursor lag and poor movement overall. I’ve also tried upgrading the driver version to the latest non-Pro flavor, which did install okay and seems to be working fine, but without a change in performance via RDP.
If there are any other ideas to try, please send them my way!
Edit: Also tried using Parsec to see if RDP was the issue - it’s not. Seems to be something with the Intel GPU side of things.
Which patches are required?
Thanks.
The only thing you need to do on proxmox is install the opt-in 6.17 kernel now. Other than that I have not had to tweak anything.
I also have the fan back under control again, but that was a bit of luck, and I need to figure out exactly what I did so I can document it here for others who may not appreciate an 8k rpm blower stuck at 100%. 
Thank you. I figured it out -except the way to make the SRIOV persistent after a Proxmox reboot.
To make it mostly persistent, add an @reboot line to your crontab and just put the echo command into it. I already had several of these for power management stuff so it was trivial to add one more.
Thanks!!
Are there any special considerations in configuring the Ubuntu VM?
When I pass through the virtual B50 my VM fails to start.
Thanks.
Hello everyone,
is anyone else having problems using the VF device in a VM? I can see the B50 VF in a VM, but when I try to use it with Immich/Frigate/Jellyfin etc., I get various errors. When I pass through the B50 completely without sr-iov, the services run.
I also see ‘Small BAR Device’ in the VM kernel logs. Large BAR is active on the host, but apparently not for the VFs in the VM. The kernel version is 6.17 on both the PVE host and in the VM.
I haven’t had any trouble with using the b50 VFs in a VM but I have also so far only used windows. This is added to my list of stuff to test when I get the time. 
Any specific error message?
Do you have any other (virtual) GPU in the system? So far in my trials it seems like I need a ‘none’ graphics device, or none at all, to get things to work properly. Which is not expected/ideal e.g. if you only want encoding and not bother setting up VNC/moonlight, but that’s how it seems to be.
The VM has a serial terminal as output. I also tried none and set the VF as primary, but same same.
It seems that the VF is only recognized as a Vulkan device, so OpenVINO and Quicksync do not appear to be supported. It works perfectly with the entire B50. So I suspect that the kernel module in 6.17 does not yet support all features. Or that support still needs to be built into ffmpeg/openvino libs.
I also just tested the DKMS kernel module 2025.11.10, but same problems and a kernel warning/error:
Device private memory not supported
With vainfo i get the following:
Trying display: wayland
error: XDG_RUNTIME_DIR is invalid or not set in the environment.
Trying display: x11
error: can't connect to X server!
Trying display: drm
libva info: VA-API version 1.22.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_22
Bus error
Interesting, in the VM Small BAR Device is displayed for me, so I checked how big the BAR is. And apparently, it’s a maximum of 2GB, regardless of how big the VF is.
Region 0: Memory at e0e80000000 (64-bit, prefetchable) [size=16M]
Region 2: Memory at e0e00000000 (64-bit, prefetchable) [size=2G]
When I divide the B50 so that the VFs have a maximum of 2GB VRAM, the message doesn’t appear and all services run again.
So it’s just because the maximum bar size in the VM is somehow 2GB.
I just wanted to ask something, has anybody else been experiencing high temps on the B50?
It’s idling in my Proxmox box and for some reason it is sitting at around 55 - 60 degrees Celsius.
Maybe I’ve configured something wrong but that seems a little high for when it’s idling. There is decent airflow in the case, as everything else is running nice and cool.
Mine idles at around 40 degrees. Can you check the card’s power consumption with nvtop?
it’s using around 20 watts. I think that is a little high for when it’s idling. Isn’t it?
Mine is much lower than that. (fluctuates but around 5-10W usually). Do you have ASPM enabled? Though that leads to fan issues sometimes…
B60 has arrived, sounds like its sitting idle for the time being…