Proxmox v7.4/v8 - Ryzen 7 7735HS - AMD Radeon 680M GPU passthrough

steps.md

This is a guide to get the Ryzen 7 7735HS with integrated graphics running with proxmox inside a Windows VM.

The guide has been migrated HERE

Hey @TSEVER thanks a lot, I also tried Ubuntu and it works well. Windows 11 had problems with setting SeaBios so I went with Win10 instead.

Hey @isc30 thanks for your guide, I'm also stuck on the vendor-reset :

× vreset.service - AMD GPU reset method to 'device_specific'
     Loaded: loaded (/etc/systemd/system/vreset.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Wed 2023-10-04 22:41:19 CEST; 7s ago
   Duration: 2ms
    Process: 1520 ExecStart=/usr/bin/bash -c echo device_specific > /sys/bus/pci/devices/0000:34:00.0/reset_method (code=exited, status=1/FAILURE)
   Main PID: 1520 (code=exited, status=1/FAILURE)
        CPU: 2ms

pve systemd[1]: Started vreset.service - AMD GPU reset method to 'device_specific'.
pve bash[1520]: /usr/bin/bash: line 1: echo: write error: Invalid argument
pve systemd[1]: vreset.service: Main process exited, code=exited, status=1/FAILURE
pve systemd[1]: vreset.service: Failed with result 'exit-code'.

When checking on the internet, I can't seem to find anything.

@Matssa56 yeah that's also what I get. There is very little information about the ryzen 7 7735hs even tho a lot of recent hardware is using it.

Maybe (?) with Proxmox v8 and kernel v6 the reset issue gets better but I couldn't manage to get passthrough working there 😢

I think the reset issue (and not being able to passthrough the "full device") could be related to having many other devices in that IOMMU group:

lspci -nn

34:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1681] (rev 0a)
34:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1640]
34:00.2 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] VanGogh PSP/CCP [1022:1649]
34:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:161d]
34:00.4 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:161e]
34:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor [1022:15e2] (rev 60)
34:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller [1022:15e3]

I'll try doing a blacklist + passthrough of all these devices and see what happens.

Edit: no luck, even passing all the devices doesn´t work. PCI passthrough for 34:00.6 directly crashes the host.

@Matssa56 yeah that's also what I get. There is very little information about the ryzen 7 7735hs even tho a lot of recent hardware is using it.

Maybe (?) with Proxmox v8 and kernel v6 the reset issue gets better but I couldn't manage to get passthrough working there 😢

I managed to make it work I think under proxmox 8 and kernel 6 with a Linux VM. I tried to make a microcode update using the proxmox helper scripts but not sure it was installed though.

I didn't have time to tinker a bit more to see if the passthrough was really working though with ffmpeg but using vainfo i saw the driver info and all so looks pretty good imo.

@Matssa56 very interesting... I just tried my method again for Ubuntu and passthrough crashes the VM. Did you do any different than the guide to get it working in Linux? If I do "lspci" from the Linux VM it appears to have everything correctly but booting the machine with the GPU as primary display crashes it

@Matssa56 very interesting... I just tried my method again for Ubuntu and passthrough crashes the VM. Did you do any different than the guide to get it working in Linux? If I do "lspci" from the Linux VM it appears to have everything correctly but booting the machine with the GPU as primary display crashes it

Well nothing in particular except the microcode update using the proxmox helper scripts. Plus I didn't put "use as primary gpu" in my memory, I'll have to take a look to be sure.

Do you have the latest bios?

So just cheked and the only thing that I didn't do was set the PCI passthrough to primary GPU, use of the proxmox helper scripts for the after install stuff and microcontrol processor update.

After installing ffmpeg and Radeontop, I can say that hardware accel using VAAPI works.

Managed to get it working on Proxmox VE8 simply following this tutorial there. I don't know why it didn't work before. I only managed to get a remote desktop using the GPU on Windows 10. Ubuntu still crashes, not sure why.

In win10, it seems like the reset issue is gone, I can stop and start the machine as many times I want and the GPU works properly every time without crashing the host. All I can say is: use the latest versions for proxmox and the kernel etc

Managed to get it working on Proxmox VE8 simply following this tutorial there. I don't know why it didn't work before. I only managed to get a remote desktop using the GPU on Windows 10. Ubuntu still crashes, not sure why.

In win10, it seems like the reset issue is gone, I can stop and start the machine as many times I want and the GPU works properly every time without crashing the host. All I can say is: use the latest versions for proxmox and the kernel etc

Nice!

Just a quick question, why add the fllowing ?

echo "softdep radeon pre: vfio-pci" >> /etc/modprobe.d/vfio.conf
echo "softdep amdgpu pre: vfio-pci" >> /etc/modprobe.d/vfio.conf
echo "softdep snd_hda_intel pre: vfio-pci" >> /etc/modprobe.d/vfio.conf

Btw the vendor reset stuff isn't necessary right? Since it doesn't work in the first place

The addition helps with the GPU reset issue, it makes vfio-pci handle the drivers in a more stable way. It seems like the changes in `pve-blacklist.conf` are not needed in VE8, only config goes inside `vfio.conf`. And no, the "vendor-reset" module on the host doesn't seem to do anything BUT the RadeonResetBugFix seems to make a difference, no idea why.

@Matssa56 Need your help :) I think I managed to isolate the specific problem that prevents Win11 from working!!!

Hey @Matssa56 what device do you have? do you mind sharing your vbios with me pls? [email protected]

I discovered that the problem seems to be when using OVMF (UEFI) for the BIOS type.
I created 2 identical VMs with Win10, 1 with SeaBIOS and the other with OVMF (UEFI). The UEFI one throws Error code 43 when trying to initialize the GPU and the seabios works properly. I'm wondering if the specific vbios I extracted from my system doesnt have UEFI support and maybe the vbios from someone else with a different motherboard works.

Please I'm out of ideas :)

FAILS: OVMF (UEFI)

WORKS: SEABIOS

@Matssa56 Need your help :) I think I managed to isolate the specific problem that prevents Win11 from working!!!

Hey @Matssa56 what device do you have? do you mind sharing your vbios with me pls? [email protected]

I discovered that the problem seems to be when using OVMF (UEFI) for the BIOS type. I created 2 identical VMs with Win10, 1 with SeaBIOS and the other with OVMF (UEFI). The UEFI one throws Error code 43 when trying to initialize the GPU and the seabios works properly. I'm wondering if the specific vbios I extracted from my system doesnt have UEFI support and maybe the vbios from someone else with a different motherboard works.

Please I'm out of ideas :)

FAILS: OVMF (UEFI)

WORKS: SEABIOS

I think I have the same device as you : minisforum UM773 lite so not really sure my vbios will be different. My Linux machine is using seabios, not the other one. Why not stick with seabios?

oh damn, did you install the latest BIOS when you got the UM773 Lite? IDK it might be nice to try if we get a different file, it's possible depending on the BIOS version and settings.

Sadly, UEFI is critical for windows 11 and other modern OS like Ubuntu if you want advanced features. If we could find someone with a different machine but same processor (maybe a SER6 PRO for example) and compare the vbios we can find exactly why UEFI isn't working on the MinisForum BIOS.

oh damn, did you install the latest BIOS when you got the UM773 Lite? IDK it might be nice to try if we get a different file, it's possible depending on the BIOS version and settings.
Sadly, UEFI is critical for windows 11 and other modern OS like Ubuntu if you want advanced features. If we could find someone with a different machine but same processor (maybe a SER6 PRO for example) and compare the vbios we can find exactly why UEFI isn't working on the MinisForum BIOS.

Yep updated the bios but it was already up to date when I received it.
Did you try the minisforum discord? I hope someone can help there :-S
You can maybe try ESXi from VMware, maybe you'll have better results?
What CPU did you use in the VM? Host?

I didn't update the BIOS so maybe that's the reason. It's a pity that I can't update the BIOS without running windows since it's an exe :( I still think that trying your up-to-date vbios might work for UEFI stuff. I used "host" for the CPU and the same config as in the guide for both (see pictures). The only difference between them is the BIOS type :O

Some links to experiment later:

• https://reddit.com/r/MiniPCs/s/oErtb0UzHq
• https://www.reddit.com/r/VFIO/comments/16mrk6j/amd_7000_seriesraphaelrdna2_igpu_passthrough/?utm_source=share&utm_medium=mweb3x&utm_name=mweb3xcss&utm_term=1&utm_content=share_button

Hey @Matssa56 @TSEVER I managed to get Win11 and UEFI working. I updated and migrated the guide to a proper repository so I could upload the ROM files there.

We can discuss in the "Discussions" or "Issues" section of the repo 👍

https://github.com/isc30/UM773-Lite-Proxmox/tree/main

Hello Everyone,

I have followed "https://github.com/isc30/UM773-Lite-Proxmox/tree/main" (thanks for tutorial), but when i stop or restart my VM using GPU passtrought (780m), i cannot start again my VM agains (error : timeout waiting on systemd), i need to restart the host.

Proxmox : 8.2.4
Linux 6.8.8-2-pve

VM Win11, UEFI, VGA none.
I use radeonresetbug without any change.

Without this case, all working fine (External monitor, no Error 43)

Hello Everyone,

I have followed "https://github.com/isc30/UM773-Lite-Proxmox/tree/main" (thanks for tutorial), but when i stop or restart my VM using GPU passtrought (780m), i cannot start again my VM agains (error : timeout waiting on systemd), i need to restart the host.

Proxmox : 8.2.4 Linux 6.8.8-2-pve

VM Win11, UEFI, VGA none. I use radeonresetbug without any change.

Without this case, all working fine (External monitor, no Error 43)

I got the same issue! when i try to restart windows 11 vm: timeout wating on systemd.

cpu: 8845hs
pve: 8.2
vm: windows 11