[SOLVED] AMD Ryzen 5700U & 7735HS iGPU passthrough Windows 11

jeenam

Member
Mar 5, 2024
46
13
8
Has anyone had success getting iGPU passthrough to work for a Ryzen 5700U CPU to Windows 11 vm? I've tried setting up GPU passthrough and am encountering the Windows error 43 issue and am unable to get it working.

System = Bosgame P1 mini pc
CPU = Ryzen 5700U
Proxmox version = 8.1-2

I extracted the VBIOS and properly configured the vm. The tutorials I've followed are:

https://www.reddit.com/r/homelab/comments/11l0s5j/boxmox_asrock_4x4_box_5800u_jbod_proxmox/
https://github.com/isc30/ryzen-7000-series-proxmox

FYI I'm not a rookie and am 100% certain my vm has been configured properly according to the writeups linked above. This leads me to believe the problem is something specific to the Vega GPU that is integrated with the Ryzen 5500U/5700U. The system was tested with Windows 10 as well and it also returned error 43.

I've searched the forums and various search engines for hours but no one has reported success with the Ryzen 5700U yet.

EDIT: Post #4 has details for setting up the Ryzen 7735HS

EDIT2: One last update. With the Ryzen 7735HS (Radeon 680M), when the Windows VM boots it takes approximately 30 seconds for the RadeonResetBugFix service to enable the iGPU. The screen resolution changes from 800x600 to native (2560x1440 in my case). Wait until the resolution automatically changes before logging in or you may get a Windows BSOD. I did not have that issue with the 5700U (Vega 8 iGPU). In fact, I didn't even need the RadeonResetBugFix.
 
Last edited:
  • Like
Reactions: pringlestuffs
Finally managed to get this working with a Ryzen 5700U. The missing piece was the UEFI ROM for the audio device of the Radeon/Vega 8 iGPU.

Be sure to read the (optional) Getting OVMF (UEFI) BIOS working: Error 43 section of the https://github.com/isc30/ryzen-7000-series-proxmox writeup. The AMDGopDriver.rom is available for download from the repo. All that's needed is to add the appropriate line to /etc/pve/qemu-server/<VM_ID>.conf to passthrough the PCI audio device after copying the file to /usr/share/kvm/.

Example code (I changed the filename to .bin instead of .rom):

hostpci1: 0000:04:00.1,pcie=1,romfile=AMDGopDriver_5700U.bin


Note that after rebooting the Windows vm for the first time after getting iGPU passthrough working, the screen resolution may be very low (e.g. 800x600). I had to manually go into Device Manager and enable the Radeon Display Adapter. Subsequent reboots did not have this problem and the Display Adapter remains enabled.

Also, the RadeonResetBugFix for Windows can be downloaded at https://github.com/inga-lovinde/RadeonResetBugFix/releases.

Thank you to the community and hope this helps others get their Ryzen iGPU up and running in passthrough mode.
 
I have Proxmox 8.1 and kernel 6.5.-13. AMD 7745hx with iGPU 610M
PCI passthrough don't crash my host or VM, but I still don't get any gpu in windows 10. AMD drivers down't detect it. So with bypass all I get is a failed default MS driver, and no devices in OS so far. I'm open to suggestions.

lspci -nn | grep -e 'AMD/ATI'
07:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Raphael [1002:164e] (rev da)
07:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt Radeon High Definition Audio Controller [1002:1640]


VM Config:

agent: 1
balloon: 0
bios: ovmf
boot: order=ide2;ide1;ide0
cores: 4
cpu: host,hidden=1,flags=+virt-ssbd;+amd-ssbd;+amd-no-ssb;+aes
efidisk0: local-lvm:vm-101-disk-0,efitype=4m,pre-enrolled-keys=1,size=4M
hostpci0: 0000:07:00.0,x-vga=1,romfile=vbios_1002_164e.bin,pcie=1
hostpci1: 0000:07:00.1,romfile=AMDGopDriver_5700U.rom,pcie=1
ide0: local:iso/virtio-win-0.1.217.iso,media=cdrom,size=519172K
ide1: local-lvm:vm-101-disk-1,size=256G
ide2: local:iso/ru_windows_10_business_editions_version_2004_updated_sep_2020_x64_dvd_0c49b616.iso,media=cdrom,size=4926594K
machine: pc-q35-8.1
memory: 16384
meta: creation-qemu=8.1.5,ctime=1709791861
name: win10
net0: virtio=BC:24:11:7D:12:FA,bridge=vmbr0,firewall=1
numa: 1
ostype: win10
scsihw: virtio-scsi-single
smbios1: uuid=b640f08e-67d5-4e7a-b636-a2b6beb0919e
sockets: 1
tpmstate0: local-lvm:vm-101-disk-2,size=4M,version=v2.0
vga: none
vmgenid: e9f3b2a3-3fad-4d88-8116-a2d5dbb8330a
 
I have Proxmox 8.1 and kernel 6.5.-13. AMD 7745hx with iGPU 610M
PCI passthrough don't crash my host or VM, but I still don't get any gpu in windows 10. AMD drivers down't detect it. So with bypass all I get is a failed default MS driver, and no devices in OS so far. I'm open to suggestions.

lspci -nn | grep -e 'AMD/ATI'
07:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Raphael [1002:164e] (rev da)
07:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt Radeon High Definition Audio Controller [1002:1640]


VM Config:

agent: 1
balloon: 0
bios: ovmf
boot: order=ide2;ide1;ide0
cores: 4
cpu: host,hidden=1,flags=+virt-ssbd;+amd-ssbd;+amd-no-ssb;+aes
efidisk0: local-lvm:vm-101-disk-0,efitype=4m,pre-enrolled-keys=1,size=4M
hostpci0: 0000:07:00.0,x-vga=1,romfile=vbios_1002_164e.bin,pcie=1
hostpci1: 0000:07:00.1,romfile=AMDGopDriver_5700U.rom,pcie=1
ide0: local:iso/virtio-win-0.1.217.iso,media=cdrom,size=519172K
ide1: local-lvm:vm-101-disk-1,size=256G
ide2: local:iso/ru_windows_10_business_editions_version_2004_updated_sep_2020_x64_dvd_0c49b616.iso,media=cdrom,size=4926594K
machine: pc-q35-8.1
memory: 16384
meta: creation-qemu=8.1.5,ctime=1709791861
name: win10
net0: virtio=BC:24:11:7D:12:FA,bridge=vmbr0,firewall=1
numa: 1
ostype: win10
scsihw: virtio-scsi-single
smbios1: uuid=b640f08e-67d5-4e7a-b636-a2b6beb0919e
sockets: 1
tpmstate0: local-lvm:vm-101-disk-2,size=4M,version=v2.0
vga: none
vmgenid: e9f3b2a3-3fad-4d88-8116-a2d5dbb8330a

I think I may have a fix for you. I've also acquired a Ryzen 7735HS w/ Radeon 680M iGPU and ran into issues with getting GPU passthrough working with it that I have resolved and believe the issues are relevant to your setup.

After configuring Proxmox to passthrough the Radeon 680M iGPU of the Ryzen 7735HS CPU, Windows 11 did not have a driver for the adapter. It showed up as 2 Microsoft Basic Display Adapters in Device Manager. I suspected the problem was Windows needed the proper driver for the 680M, and I was correct. Use this link to download the latest AMD Radeon drivers for Windows 11.

Direct Link - https://drivers.amd.com/drivers/whq...lin-edition-24.2.1-win10-win11-feb26-rdna.exe


When you install the driver package, I HIGHLY advise performing the 'driver only' method. The reason is I initially had problems after the driver installed and I had to do a reboot of my Proxmox server. After rebooting, Windows reported the Radeon 680M was disabled, so I immediately installed the RadeonResetBugFix. The file is available at https://github.com/inga lovinde/Rad.../download/v0.1.7/RadeonResetBugFixService.exe. After I enabled the Radeon 680M in Device Manager Windows BSOD'd a few minutes later and I rebooted my Proxmox server again. After that reboot I configured the vm to use the iGPU as the Primary GPU and Windows booted without any problems. I then installed the AMD driver package again, this time selecting the full install to add the Adrenalin software. So far it's been stable and has not crashed again. If there are any stability issues I will send you a message and report back to this thread.

Hope this helps you out.
 
Last edited:
  • Like
Reactions: pringlestuffs
Windows 11 has been stable. However, when Windows starts, it takes about 20 seconds to enable the Radeon Display Adapter due to the RadeonResetBugFix service. Other than that, no issues. It has been completely stable.
 
Last edited:
It looks like black magic. Thank you for driver link.

I tried before several versions of adrenalin drivers from amd site. One from 2022 (recommended version for 610M), new from 2024. And in both cases I can't pass AMD hardware test. Each time they just say 'No AMD hardware detected' and nothing happens.

After your drivers windows finally recognise my iGPU. I successfully install several small games to test it. they all give very strange resolution (I opted remote to 1080p), and games looks like they show 1/4 of screen. I will try to fix it.

About reset fix. I installed to Proxmox host a reset service. so far it worked ok if I don't restart VM. if I do it then sometimes it don't reset it. If I make a delay 1-2min between shutdown and start than usually everything worked ok. I will test it.

I will try to use passthrough in my guest VM in steamOs and MacOs. Windows experience looks promising.
 
  • Like
Reactions: jeenam
Do you try something for better screen sharing performance other than Remote Desktop? It is in my list. Some users mentioned problems with iGPU in that case.
 
I only use RDP for remote desktop so can't comment on screen sharing.

No problems with screen resolution with my setup. Everything runs fullscreen as expected. Tested with Quake Champions, Halo Infinite, Quake 2 and CS 2.
 
Last edited:
I'm using a GMKTEC M5PRO with a Ryzen 5700U and I'm totally lost.
Nothing is working in my case do you know how to fix it? I am already really giving up looking for 4 days.
Code:
root@node1:~# lspci -nn | grep -e 'AMD/ATI'
06:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Lucienne [1002:164c] (rev c1)
06:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Radeon High Definition Audio Controller [1002:1637]

and i have

root@node1:~# lspci -knns 06:00.0
06:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Lucienne [1002:164c] (rev c1)
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Lucienne [1002:1636]
Kernel driver in use: vfio-pci
Kernel modules: amdgpu

1714033076459.png

args: -cpu 'host,-hypervisor,kvm=off'
bios: ovmf
boot: order=virtio0;net0
cores: 4
cpu: host
efidisk0: local-zfs:vm-100-disk-0,efitype=4m,pre-enrolled-keys=1,size=1M
hostpci0: 0000:06:00.0,pcie=1,romfile=vbios_5700U.bin,x-vga=1
hostpci1: 0000:06:00.1,pcie=1,romfile=AMDGopDriver_5700U.bin
kvm: 1
machine: pc-q35-8.1
memory: 8192
meta: creation-qemu=8.1.2,ctime=1706170004
name: Windows
net0: virtio=BC:24:11:9F:1C:79,bridge=vmbr0,firewall=1
numa: 0
onboot: 1
ostype: win11
scsihw: virtio-scsi-single
smbios1: uuid=e3c72ae3-19b4-4bbf-a6de-3eb8d7d45e98
sockets: 1
tpmstate0: local-zfs:vm-100-disk-1,size=4M,version=v2.0
vga: none
virtio0: local-zfs:vm-100-disk-2,iothread=1,size=100G
vmgenid: ca04c572-92e0-4790-9d74-ee4c8663653b
 
Last edited:
Are you able to boot into Windows? If you can boot into Windows but the Radeon Display Device shows error 43 you need to install the AMD driver for the video card. You'll need the full driver package installer and not the smaller package that auto-detects devices.

This is the link to the Windows 11 driver - https://drivers.amd.com/drivers/whq...ion-24.3.1-win10-win11-mar20-vega-polaris.exe
In that case, I'm doing everything from the beginning and will let you know right away
 
The driver installer may crash Windows. If it does, just run it again and it will eventually complete successfully. Also, install the RadeonResetBugFix after you install the Windows 11 Radeon driver - https://github.com/inga-lovinde/Rad.../download/v0.1.7/RadeonResetBugFixService.exe.

With the RadeonResetBugFix, when Windows starts, it takes about 30 seconds to enable the Radeon Display Adapter due to the RadeonResetBugFix service. With the 7735HS w/ Radeon 680M the login window would initially be displayed at a low resolution and after the service started it would then refresh to normal (2536x1440 for my monitor). If you login before the service starts it may cause Windows to BSOD, so wait for the service to correct the display resolution before logging into Windows. Note this behavior does not occur with 7840HS w/ Radeon 780M. That CPU/iGPU doesn't have to refresh the display resolution before logging in.
 
Last edited:
You need to modify the line in your 104.conf for the audio device. It needs to be:

hostpci1: 0000:06:00.1,pcie=1,romfile=AMDGopDriver_5700U.rom

Also, the instructions on the github page say to install Windows before making the modifications to configure the VM for GPU passthrough. In other words, Windows needs to be installed before you configure GPU passthrough.
 
Last edited:
You need to modify the line in your 104.conf for the audio device. It needs to be:

hostpci1: 0000:06:00.1,pcie=1,romfile=AMDGopDriver_5700U.rom

Also, the instructions on the github page say to install Windows before making the modifications to configure the VM for GPU passthrough. In other words, Windows needs to be installed before you configure GPU passthrough.


Unfortunately still the same, but you can already see the rom in proxmox
I installed the first windows according to the instructions, then installed VIRTIO AMD GPU DRIVER and RadeonResetBugFIX


1714066964863.png


The driver also appears to be installed

1714067002720.png
1714067025497.png
 

Attachments

  • 1714066955000.png
    1714066955000.png
    68.4 KB · Views: 8
Last edited:
Hi I have a GMKTEC M5 PRO with bios version v1.0.3
I have tested with a jeenam all possible solutions, from windows 11 to windows 10 and seabios and OVMF.
We are running out of ideas, we did a Proxmox format and still nothing.
My processor is a Ryzen 5700U with IOMMU and SR-IOV enabled in the bios and this is my configuration does anyone know how to fix the problem?
the Radeon Windows driver installs OK
the problem is that the GPU is not outputing any display to the monitor from Windows
it's still showing the display output from the Proxmox OS
Let me add right away that I tried adding just the drivers and the full installation :)
 

Attachments

  • 325806639-9a5be07c-5c5d-4b98-9f13-7c30a48ec000.png
    325806639-9a5be07c-5c5d-4b98-9f13-7c30a48ec000.png
    11.6 KB · Views: 18
  • 325806674-c45a0a86-709c-4d6a-867c-86a6a0ff0ba4.png
    325806674-c45a0a86-709c-4d6a-867c-86a6a0ff0ba4.png
    26.2 KB · Views: 16
  • 325806722-cd5959a4-742e-4706-9ed2-adb6c81b5e43.png
    325806722-cd5959a4-742e-4706-9ed2-adb6c81b5e43.png
    14.9 KB · Views: 12
  • 325806778-af4740d9-82b4-4654-88f3-e6cf4fcdb870.png
    325806778-af4740d9-82b4-4654-88f3-e6cf4fcdb870.png
    7.9 KB · Views: 11
  • 325806826-e9f1022f-4acf-4a5b-8312-6906d687a681.png
    325806826-e9f1022f-4acf-4a5b-8312-6906d687a681.png
    107.9 KB · Views: 12
  • 325807144-f3a7c8f1-c6e3-44af-8215-ff2d67e75fa8.png
    325807144-f3a7c8f1-c6e3-44af-8215-ff2d67e75fa8.png
    40.7 KB · Views: 13
  • 325815181-54f2c9b1-776c-4470-a158-03a92135b625.png
    325815181-54f2c9b1-776c-4470-a158-03a92135b625.png
    10.9 KB · Views: 15
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!