Assistance with Passing Through Ryzen 5 5600G Integrated GPU to VM/Linux Mint

usrad

New Member
Feb 10, 2024
3
0
1
I am seeking assistance with passing through the integrated GPU from a Ryzen 5 5600G to either a VM with several LXC containers or directly to a Linux Mint VM. I have successfully passed through an AMD RX 580 GPU to a Windows 11 VM, and it works flawlessly. However, I'm encountering issues with the integrated GPU passthrough.

Host System Configuration:

CPU: Ryzen 5 5600G with integrated GPU
Motherboard: Steel Legend B550
Proxmox VE Version: 8.1.4
Additional PCI Devices: AMD RX 580 GPU (successfully passed through to Windows 11 VM)

Steps Taken:

Enabled IOMMU in BIOS/UEFI settings, with amd_iommu=on and iommu=pt set in GRUB configuration.
Identified the IOMMU group for the Ryzen 5 5600G integrated GPU using lspci -nnv. The GPU appears under 07:00.0.
Attempted Passthrough Configuration for the integrated GPU by adding hostpci0: 07:00.0,pcie=1,x-vga=on to the VM's configuration file (/etc/pve/qemu-server/<vmid>.conf).
VM Startup Issues: Encountered errors when starting the VM, specifically: kvm: ../hw/pci/pci.c:1637: pci_irq_handler: Assertion '0 <= irq_num && irq_num < PCI_NUM_PINS' failed. start failed: QEMU exited with code 1.

Troubleshooting Steps:

Ensured all system and Proxmox packages are up to date.
Verified and tried different machine types (q35 and i440fx).
Checked for any conflicting BIOS/UEFI settings that might affect passthrough.
Attempted to isolate the GPU passthrough issue by excluding the audio component of the integrated GPU.
Despite these efforts, the integrated GPU passthrough to the VM/Linux Mint has not been successful. I am looking for guidance on how to properly configure the passthrough for the Ryzen 5 5600G's integrated GPU, or any insights into potential issues with my current setup.

Any advice, suggestions, or shared experiences with similar hardware would be greatly appreciated. Thank you in advance for your assistance.
 
I just recently managed to pass trough my 5600g iGPU to a windows VM.

I have exactly the same motherboard.
Have used the ACS overide before to passtrough a SAS controller from the second PCI-ex16 slot.

Am using a windows 10 VM, UEFI, q35 and CPU=host.

Ran into code 43 after driver install. Adding ROM file from somewhere on this forum for a 5600g fixed it for me.
Now works fine but run into AMD reset bug.

Took me a while to get this far, but glad it works.
 
I just recently managed to pass trough my 5600g iGPU to a windows VM.

I have exactly the same motherboard.
Have used the ACS overide before to passtrough a SAS controller from the second PCI-ex16 slot.

Am using a windows 10 VM, UEFI, q35 and CPU=host.

Ran into code 43 after driver install. Adding ROM file from somewhere on this forum for a 5600g fixed it for me.
Now works fine but run into AMD reset bug.

Took me a while to get this far, but glad it works.

I did a simple edit and added the vendor ID (=0x1638) of 5600G to _AMD_NAVI10 in device-db.h in vendor-reset, so it will reset the GPU the same way as NAVI10. And this seems to do the trick. If you do this don't forget to add your ID to the udev rule also, or if you use manual script to modprobe vendor_reset and also to set reset_method to "device_specific".

If I understand the "amdgpu" driver correctly, then it knows how to do proper resets for most cards and there are only a view relevant combinations for all of them. So chances are high with trial and error that you can make vendor-reset work, by simply adding your card's vendor ID to this file, so it performs one of the vega10, vega20, navi10 or polaris10 reset procedures.

I was now able to reload my Windows VM with 5600G's Vega 7 GPU many times without ever rebooting my host machine. And it would show eventually with Code 43. But I could fix this by loading Qemu in UEFI mode with romfile=vgabios-cezanne-uefi.bin plus installing Niemez drivers RDNA 24.3.1 long enterprise V5.5/23.40. Then I only needed to plug a vga cable from motherboard into my monitor for Looking Glass to work (GPU shuts off output if there is no resistance on wires), but Remote Desktop is accelerated either way.

You can read my full experiences in this thread: https://forum.proxmox.com/threads/amd-ryzen-5600g-igpu-code-43-error.138665/post-726791
 
Last edited: