Passtrough AMD Ryzen 7 5825U

A

alex-fl

New Member
Apr 16, 2024
11
1
3
Hi everyone,

I recently bought a small home server and installed Proxmox. On one of the VMs (Debian), I’m running Jellyfin and I want to passthrough the AMD Ryzen 7 5825U IGPU.

The Wi-Fi passthrough worked without any issues, and I think it's because it has its own IOMMU group.

Proxmox Node Information:​

  • OS Release:
Code: 
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"

  • Proxmox Version:
Code: 
pve-manager/8.3.0/c1689ccb1065a83b (running kernel: 6.8.12-4-pve)

​

Hardware Information:​

  • AMD IGPU (Barcelo) and WI-FI
lspci -nn | grep -e 'AMD/ATI'
lspci -nn | grep -e 'Wi-Fi'
Code: 
04:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723] (rev 1a)
        Subsystem: Intel Corporation Wi-Fi 6 AX200NGW [8086:0084]
        Kernel driver in use: vfio-pci
        Kernel modules: iwlwifi
05:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Barcelo [1002:15e7] (rev c1)
        Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Barcelo [1002:0123]
        Kernel driver in use: vfio-pci
        Kernel modules: amdgpu
05:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Radeon High Definition Audio Controller [1002:1637]
        Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Radeon High Definition Audio Controller [1002:1637]
        Kernel driver in use: vfio-pci
        Kernel modules: snd_hda_intel



GRUB Configuration:
cat /etc/default/grub
Code: 
GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet iommu=pt"
#GRUB_CMDLINE_LINUX="pcie_acs_override=downstream,multifunction"

  • dmesg | grep -e DMAR -e IOMMU
Code: 
[    0.372637] pci 0000:00:00.2: AMD-Vi: IOMMU performance counters supported
[    0.405945] perf/amd_iommu: Detected AMD IOMMU #0 (2 banks, 4 counters/bank).

  • dmesg | grep 'remapping'
Code: 
[    0.373616] AMD-Vi: Interrupt remapping enabled





VFIO Modules:
cat /etc/modules
Code: 
vfio
vfio_iommu_type1
vfio_pci
vfio_virqfd

VFIO Config:
cat /etc/modprobe.d/vfio.conf
Code: 
softdep amdgpu pre: vfio-pci
softdep snd_hda_intel pre: vfio-pci
softdep iwlwifi pre: vfio-pci
options vfio-pci ids=8086:2723,1002:15e7,1002:1637



VM Configuration:
cat /etc/pve/qemu-server/1010.conf
Code: 
#scsi1%3A data%3Avm-1010-disk-0,backup=0,iothread=1,size=5000G
agent: 1
args: -cpu 'host,-hypervisor,kvm=off'
bios: ovmf
boot: order=ide2;scsi1;scsi0
cores: 16
cpu: host
hostpci0: 0000:05:00.0,pcie=1,romfile=vbios_5825U_org.bin,x-vga=1
hostpci1: 0000:05:00.1,pcie=1,romfile=AMDGopDriver_5800H.rom
ide2: none,media=cdrom
machine: q35,viommu=virtio
memory: 16384
meta: creation-qemu=9.0.2,ctime=1731457697
name: Docker-Server
net0: virtio=BC:24:11:86:9D:56,bridge=vmbr1,firewall=1
numa: 1
onboot: 1
ostype: l26
scsi0: local-lvm:vm-1010-disk-1,iothread=1,size=218942668
scsi1: local-lvm:vm-1010-disk-0,iothread=1,size=100G
scsi2: data:vm-1010-disk-0,iothread=1,size=5000G
scsihw: virtio-scsi-single
smbios1: uuid=5aa91c0a-f654-4fa8-a3d0-0513aead97a3
sockets: 1
unused3: local-lvm:vm-1010-disk-3
vga: qxl
vmgenid: 401c533f-d810-41ec-bf4e-6bb2e539e9e2

Debian VM

cat /etc/os-release
Code: 
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"

uname -r
Code: 
6.1.0-27-amd64


  • Error Logs (journalctl -b)
Code: 
Nov 30 03:16:41 docker-server kernel: smpboot: CPU0: AMD Ryzen 7 5825U with Radeon Graphics (family: 0x19, model: 0x50, ste\
pping: 0x0)
Nov 30 03:16:41 docker-server kernel: AMD-Vi: AMD IOMMUv2 functionality not available on this system - This is not a bug.
Nov 30 03:16:41 docker-server kernel: smpboot: CPU0: AMD Ryzen 7 5825U with Radeon Graphics (family: 0x19, model: 0x50, ste\
pping: 0x0)
Nov 30 03:55:55 docker-server kernel: amdgpu 0000:01:00.0: firmware: direct-loading firmware amdgpu/green_sardine_asd.bin
Nov 30 03:55:55 docker-server kernel: amdgpu 0000:01:00.0: firmware: direct-loading firmware amdgpu/green_sardine_ta.bin
Nov 30 03:55:55 docker-server kernel: amdgpu 0000:01:00.0: amdgpu: PSP runtime database doesn't exist
Nov 30 03:55:55 docker-server kernel: amdgpu 0000:01:00.0: amdgpu: PSP runtime database doesn't exist
Nov 30 03:55:55 docker-server kernel: amdgpu 0000:01:00.0: firmware: direct-loading firmware amdgpu/green_sardine_vcn.bin
Nov 30 03:55:55 docker-server kernel: [drm] Found VCN firmware Version ENC: 1.23 DEC: 8 VEP: 0 Revision: 1
Nov 30 03:55:55 docker-server kernel: amdgpu 0000:01:00.0: amdgpu: Will use PSP to load VCN firmware
Nov 30 03:55:55 docker-server kernel: Huh? What family is it: 0x19?!
Nov 30 03:55:56 docker-server systemd[1]: etc-machine\x2did.mount: Deactivated successfully.
Nov 30 03:55:58 docker-server kernel: [drm] reserve 0x400000 from 0xf41f800000 for PSP TMR
Nov 30 03:56:01 docker-server kernel: [drm] psp gfx command UNKNOWN CMD(0x0) failed and response status is (0x0)
Nov 30 03:56:01 docker-server kernel: [drm:psp_hw_start [amdgpu]] *ERROR* PSP load tmr failed!
Nov 30 03:56:01 docker-server kernel: [drm:psp_hw_init [amdgpu]] *ERROR* PSP firmware loading failed
Nov 30 03:56:01 docker-server kernel: [drm:amdgpu_device_fw_loading [amdgpu]] *ERROR* hw_init of IP block <psp> failed -22
Nov 30 03:56:01 docker-server kernel: amdgpu 0000:01:00.0: amdgpu: amdgpu_device_ip_init failed
Nov 30 03:56:01 docker-server kernel: amdgpu 0000:01:00.0: amdgpu: Fatal error during GPU init
Nov 30 03:56:01 docker-server kernel: amdgpu 0000:01:00.0: amdgpu: amdgpu: finishing device.



  • lspci -v
Code: 
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Barcelo (rev c1) (prog-if 00 [VGA controller])
        Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Barcelo
        Physical Slot: 0
        Flags: fast devsel, IRQ 16, IOMMU group 11
        .......

        Kernel modules: amdgpu

02:00.0 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Radeon High Definition Audio Controller
        Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Radeon High Definition Audio Controller
        Physical Slot: 0-2
        Flags: bus master, fast devsel, latency 0, IRQ 57, IOMMU group 12
        .....

        Kernel driver in use: snd_hda_intel
        Kernel modules: snd_hda_intel


Issue:​

I am encountering an error when trying to initialize the GPU device on the Debian VM. The error logs indicate issues with loading the PSP firmware, specifically the PSP runtime database and PSP firmware loading failures.

Interestingly, the IGPU passthrough works fine in a Windows VM, but I haven't been able to get it working in Debian.

Has anyone faced this issue or have suggestions for resolving it? Any help would be greatly appreciated!
 
Last edited:
dustojnikhummer said:
Well, I tried your guide and sadly nothing. Tried VMs in i440fx-q35, SeaBIOS or UEFI, x-gpu on and off.
Host loses image but the VM never starts, not even an error message. Yes, my iGPU is in it's own group
Click to expand...
Did you look is there error in pve system logs and looked vm cpu usage and if it stuck at a certain percentage in that case it just need full node reboot.
Or did you mean that vm stays stopped and not changing status to running
if vm host loses image and not showing "not running image" i think its starting and you need use ssh or putty to connect to vm just wait to vm start.
but if you did all these test without rebooting full node in between changes then i think amd reset bug blocked vm booting, i noticed that when i made that "guide" for myself and if you are changing machine type then there maybe network card problem because every time you change machine type i440fx vs q35 network card name changes so ip changes.

So first test you can connect with ssh and then passtrough only gpu not all devices because it will not work with aoostart, my device also says its own iommu group.
If you leave all functions enabled it includes all devices at 0000:05:00.X. and wont start and igpu get stuck and need full node reboot.

here is my full test vm conf file.
Code: 
gent: 1
balloon: 0
boot: order=scsi0;net0
cores: 8
cpu: host
hostpci0: 0000:05:00.0,romfile=vbios_1002.bin,x-vga=1
memory: 8192
meta: creation-qemu=7.2.0,ctime=1678619349
name: test-1
net0: virtio=36:2D:XX:XX:XX:XX,bridge=vmbr10,firewall=1
numa: 0
onboot: 1
ostype: l26
scsi0: local-lvm:vm-819-disk-0,discard=on,iothread=1,size=40G,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=39e46b92-XXXX-XXXX-XXXX-e2a51577ec84
sockets: 1
vmgenid: 81defa87-XXXX-XXXX-XXXX-1f9903ed65ea
 
DjEsko said:
Did you look is there error in pve system logs and looked vm cpu usage and if it stuck at a certain percentage in that case it just need full node reboot.
Or did you mean that vm stays stopped and not changing status to running
if vm host loses image and not showing "not running image" i think its starting and you need use ssh or putty to connect to vm just wait to vm start.
but if you did all these test without rebooting full node in between changes then i think amd reset bug blocked vm booting, i noticed that when i made that "guide" for myself and if you are changing machine type then there maybe network card problem because every time you change machine type i440fx vs q35 network card name changes so ip changes.

So first test you can connect with ssh and then passtrough only gpu not all devices because it will not work with aoostart, my device also says its own iommu group.
If you leave all functions enabled it includes all devices at 0000:05:00.X. and wont start and igpu get stuck and need full node reboot.

here is my full test vm conf file.
Code: 
gent: 1
balloon: 0
boot: order=scsi0;net0
cores: 8
cpu: host
hostpci0: 0000:05:00.0,romfile=vbios_1002.bin,x-vga=1
memory: 8192
meta: creation-qemu=7.2.0,ctime=1678619349
name: test-1
net0: virtio=36:2D:XX:XX:XX:XX,bridge=vmbr10,firewall=1
numa: 0
onboot: 1
ostype: l26
scsi0: local-lvm:vm-819-disk-0,discard=on,iothread=1,size=40G,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=39e46b92-XXXX-XXXX-XXXX-e2a51577ec84
sockets: 1
vmgenid: 81defa87-XXXX-XXXX-XXXX-1f9903ed65ea
Click to expand...
No, the VM never started. Proxmox host lost image but I didn't lose the web terminal. There was no process for the VM in htop either, no DHCP request either. Of course I did a full reboot between attempts.

Anyway, I gave up on this and just use it as a NAS now. If I need GPU accelerated workloads on it I will just use LXC containers, but thanks for your help. Hopefully others get it working too.
 
dustojnikhummer said:
It works for you with an EFI OS? What is in the VM?
Click to expand...
yes with EFI

Operating System: Debian GNU/Linux 12 (bookworm)
Kernel: Linux 6.1.0-29-amd64
Architecture: x86-64
Hardware Vendor: QEMU
Hardware Model: Standard PC _Q35 + ICH9, 2009_
Firmware Version: 4.2023.08-4
 
alex-fl said:
yes with EFI

Operating System: Debian GNU/Linux 12 (bookworm)
Kernel: Linux 6.1.0-29-amd64
Architecture: x86-64
Hardware Vendor: QEMU
Hardware Model: Standard PC _Q35 + ICH9, 2009_
Firmware Version: 4.2023.08-4
Click to expand...
Shame you didn't get this working two weeks back, I just removed Proxmox from my NAS lol. Glad it's working now though!
 
dustojnikhummer said:
Shame you didn't get this working two weeks back, I just removed Proxmox from my NAS lol. Glad it's working now though!
Click to expand...
"I actually did... but didn't take any notes ^^ I had a problem and couldn't get Proxmox started, so I had to redo everything. This time, I figured I'd better write it down!" ^^
 
alex-fl said:
"I actually did... but didn't take any notes ^^ I had a problem and couldn't get Proxmox started, so I had to redo everything. This time, I figured I'd better write it down!" ^^
Click to expand...
Would you be willing to do some more testing? Can you see if it also works in a Windows guest? Or better yet, with functional video output to a physical monitor? (You seem to be knowing what you are doing lol)
 
"Haha, trial and error... but I tested it first with Windows, and it worked. I followed the guide from this GitHub repo and made the adjustments from my post with the blacklist."
 
hi all! I'm following Alex's guide, but i'm stuck at this point ls /dev/dri/

Code: 
ls: cannot access '/dev/dri/': No such file or directory
 
You restart also the proxmox host?
You followed befor a other guid?

You need to give us more infos for help:

lspci -nn | grep -e 'AMD/ATI'
cat /etc/default/grub
cat /etc/modules
cat /etc/modprobe.d/vfio.conf
ls -l /usr/share/kvm/
cat /etc/pve/qemu-server/<VM_ID>.conf
 
lspci -nn | grep -e 'AMD/ATI'

Code: 
06:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Barcelo [1002:15e7] (rev c1)
06:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Radeon High Definition Audio Controller [1002:1637]

cat /etc/default/grub

Code: 
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet amd_iommu=on iommu=pt"
GRUB_CMDLINE_LINUX=""

# If your computer has multiple operating systems installed, then you
# probably want to run os-prober. However, if your computer is a host
# for guest OSes installed via LVM or raw disk devices, running
# os-prober can cause damage to those guest OSes as it mounts
# filesystems to look for things.
#GRUB_DISABLE_OS_PROBER=false

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"

cat /etc/modules

Code: 
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
# Parameters can be specified after the module name.

vfio
vfio_iommu_type1
vfio_pci
vfio_virqfd
vfio
vfio_iommu_type1
vfio_pci
vfio_virqfd
vfio
vfio_iommu_type1
vfio_pci
vfio_virqfd
vfio
vfio_iommu_type1
vfio_pci
vfio_virqfd
vfio
vfio_iommu_type1
vfio_pci
vfio_virqfd
vfio
vfio_iommu_type1
vfio_pci
vfio_virqfd

cat /etc/modprobe.d/vfio.conf

Code: 
options vfio-pci ids=1002:15e7,1002:1637
softdep amdgpu pre: vfio-pci
softdep snd_hda_intel pre: vfio-pci
options vfio-pci ids=1002:15e7,1002:1637
softdep amdgpu pre: vfio-pci
softdep snd_hda_intel pre: vfio-pci
options vfio-pci ids=1002:1637
softdep radeon pre: vfio-pci
softdep amdgpu pre: vfio-pci
softdep snd_hda_intel pre: vfio-pci
options vfio-pci ids=1002:15e7,1002:1637
softdep radeon pre: vfio-pci
softdep amdgpu pre: vfio-pci
softdep snd_hda_intel pre: vfio-pci
options vfio-pci ids=1002:15e7,1002:1637
softdep amdgpu pre: vfio-pci
softdep snd_hda_intel pre: vfio-pci
options vfio-pci ids=1002:15e7,1002:1637
softdep amdgpu pre: vfio-pci
softdep snd_hda_intel pre: vfio-pci

ls -l /usr/share/kvm/

Code: 
total 318256
-rw-r--r-- 1 root root    75776 Mar 30 22:01 AMDGopDriver-5825U.rom
-rw-r--r-- 1 root root   262144 Apr 29  2024 bios-256k.bin
-rw-r--r-- 1 root root   131072 Apr 29  2024 bios.bin
-rw-r--r-- 1 root root   131072 Apr 29  2024 bios-microvm.bin
-rw-r--r-- 1 root root 67108864 Feb 24 17:33 edk2-aarch64-code.fd
-rw-r--r-- 1 root root 67108864 Feb 24 17:33 edk2-arm-code.fd
-rw-r--r-- 1 root root 67108864 Feb 24 17:33 edk2-arm-vars.fd
-rw-r--r-- 1 root root  3653632 Feb 24 17:33 edk2-i386-code.fd
-rw-r--r-- 1 root root  3653632 Feb 24 17:33 edk2-i386-secure-code.fd
-rw-r--r-- 1 root root   540672 Feb 24 17:33 edk2-i386-vars.fd
-rw-r--r-- 1 root root    42903 May 21  2023 edk2-licenses.txt
-rw-r--r-- 1 root root 16777216 Feb 24 17:33 edk2-loongarch64-code.fd
-rw-r--r-- 1 root root 16777216 Feb 24 17:33 edk2-loongarch64-vars.fd
-rw-r--r-- 1 root root 33554432 Feb 24 17:33 edk2-riscv-code.fd
-rw-r--r-- 1 root root 33554432 Feb 24 17:33 edk2-riscv-vars.fd
-rw-r--r-- 1 root root  3653632 Feb 24 17:33 edk2-x86_64-code.fd
-rw-r--r-- 1 root root  3653632 Feb 24 17:33 edk2-x86_64-secure-code.fd
-rw-r--r-- 1 root root   159232 May 21  2023 efi-e1000e.rom
-rw-r--r-- 1 root root   159232 May 21  2023 efi-e1000.rom
-rw-r--r-- 1 root root   159232 May 21  2023 efi-eepro100.rom
-rw-r--r-- 1 root root   157696 May 21  2023 efi-ne2k_pci.rom
-rw-r--r-- 1 root root   157696 May 21  2023 efi-pcnet.rom
-rw-r--r-- 1 root root   160768 May 21  2023 efi-rtl8139.rom
-rw-r--r-- 1 root root   160768 May 21  2023 efi-virtio.rom
-rw-r--r-- 1 root root   156672 May 21  2023 efi-vmxnet3.rom
drwxr-xr-x 2 root root     4096 Mar 28 18:54 firmware
drwxr-xr-x 2 root root     4096 Mar 28 18:54 keymaps
-rw-r--r-- 1 root root     9216 May 21  2023 kvmvapic.bin
-rw-r--r-- 1 root root     1024 May 21  2023 linuxboot.bin
-rw-r--r-- 1 root root     1536 May 21  2023 linuxboot_dma.bin
-rw-r--r-- 1 root root     3082 Feb 24 17:33 machine-versions-x86_64.json
-rw-r--r-- 1 root root     1024 May 21  2023 multiboot.bin
-rw-r--r-- 1 root root     1024 May 21  2023 multiboot_dma.bin
-rw-r--r-- 1 root root      768 May 21  2023 npcm7xx_bootrom.bin
-rw-r--r-- 1 root root  1966080 May 21  2023 OVMF_CODE-pure-efi.fd
-rw-r--r-- 1 root root   131072 May 21  2023 OVMF_VARS-pure-efi.fd
-rw-r--r-- 1 root root     1536 May 21  2023 pvh.bin
-rw-r--r-- 1 root root    67072 May 21  2023 pxe-e1000.rom
-rw-r--r-- 1 root root    61440 May 21  2023 pxe-eepro100.rom
-rw-r--r-- 1 root root    61440 May 21  2023 pxe-ne2k_pci.rom
-rw-r--r-- 1 root root    61440 May 21  2023 pxe-pcnet.rom
-rw-r--r-- 1 root root    61440 May 21  2023 pxe-rtl8139.rom
-rw-r--r-- 1 root root    60416 May 21  2023 pxe-virtio.rom
-rwxr-xr-x 1 root root    65536 May 21  2023 qboot.rom
-rw-r--r-- 1 root root      850 May 21  2023 QEMU,cgthree.bin
-rw-r--r-- 1 root root   154542 May 21  2023 qemu-nsis.bmp
-rw-r--r-- 1 root root     1402 May 21  2023 QEMU,tcx.bin
-rw-r--r-- 1 root root     4148 Feb 24 17:33 recognized-CPUID-flags-x86_64
-rw-r--r-- 1 root root  2527328 Apr 29  2024 skiboot.lid
-rw-r--r-- 1 root root   513990 Feb 24 17:33 trace-events-all
-rw-r--r-- 1 root root   524288 May 21  2023 u-boot-sam460-20100605.bin
-rw-r--r-- 1 root root    55296 Mar 30 22:00 vbios_5825U.bin
-rw-r--r-- 1 root root    55296 Mar 29 21:19 vbios_7xxx.bin
-rw-r--r-- 1 root root    39424 Apr 29  2024 vgabios-ati.bin
-rw-r--r-- 1 root root    38912 Apr 29  2024 vgabios.bin
-rw-r--r-- 1 root root    28672 Apr 29  2024 vgabios-bochs-display.bin
-rw-r--r-- 1 root root    38912 Apr 29  2024 vgabios-cirrus.bin
-rw-r--r-- 1 root root    39424 Apr 29  2024 vgabios-qxl.bin
-rw-r--r-- 1 root root    28672 Apr 29  2024 vgabios-ramfb.bin
-rw-r--r-- 1 root root    39424 Apr 29  2024 vgabios-stdvga.bin
-rw-r--r-- 1 root root    39424 Apr 29  2024 vgabios-virtio.bin
-rw-r--r-- 1 root root    39424 Apr 29  2024 vgabios-vmware.bin
drwxr-xr-x 2 root root     4096 Mar 28 18:54 vhost-user
-rwxr-xr-x 1 root root     3456 May 21  2023 vof.bin
-rw-r--r-- 1 root root    16384 May 21  2023 vof-nvram.bin

cat /etc/pve/qemu-server/104.conf (Windows 11 VM)

Code: 
agent: 1
balloon: 4096
bios: ovmf
boot: order=scsi0;ide0;ide2;net0
cores: 6
cpu: x86-64-v2-AES
efidisk0: storage:104/vm-104-disk-0.qcow2,efitype=4m,size=528K
ide0: storage:iso/virtio-win-0.1.266.iso,media=cdrom,size=707456K
ide2: storage:iso/tiny11.iso,media=cdrom,size=5891728K
machine: pc-q35-9.2
memory: 6144
meta: creation-qemu=9.2.0,ctime=1743333884
name: windows11
net0: virtio=BC:24:11:2C:6D:F8,bridge=vmbr0,firewall=1
numa: 0
ostype: win11
scsi0: local-lvm:vm-104-disk-0,cache=writeback,discard=on,iothread=1,size=250G,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=00d144e5-0035-47c7-a4a5-38daae8f7ef5
sockets: 1
tpmstate0: storage:104/vm-104-disk-1.raw,size=4M,version=v2.0
vmgenid: 44a5e768-98c1-45d2-9797-4e18daeb584b

I also have the VM 1010, with these in the hardware section

Code: 
hostpci0: 0000:06:00.0,romfile=vbios_5825U.bin,x-vga=1
hostpci1: 0000:06:00.1,romfile=AMDGopDriver-5825U.rom
 
Last edited:
leviackerman91

You want to be helped, right?

I'm investing my free time here to assist you.

A little structuring of a post, multiple paragraphs, various code blocks, and maybe a short description of what each file is (like in my first post or on GitHub) shouldn't be too much to ask.

Like this, I have no motivation to help… If you can't manage that, at least use ChatGPT to structure it.

Best regards from my free time.
 
Last edited:
  • Like
Reactions: leviackerman91
alex-fl said:
leviackerman91

You want to be helped, right?

I'm investing my free time here to assist you.

A little structuring of a post, multiple paragraphs, various code blocks, and maybe a short description of what each file is (like in my first post or on GitHub) shouldn't be too much to ask.

Like this, I have no motivation to help… If you can't manage that, at least use ChatGPT to structure it.

Best regards from my free time.
Click to expand...

Sorry Alex, i edited my previous post, i hope it's more clear now.

Of course i didn't meant to offend you any way and i really appreciate your help. Please keep in mind that is my first time with Proxmox and VMs, so i'm still learning and trying to figure out things
 
Last edited:
Okay, that looks better.
So, if VM1010 is using the VBIOS of the GPU, please also provide the configuration of that VM. Otherwise, it won’t be useful.

Here in the forum, especially in the Linux section, it is important that you also do your own research, ask yourself critical questions about whether it can work, and think logically.

I also have little knowledge of Proxmox. I just managed to get it working through trial and error and a bit of luck.

However, your configuration files look much worse.


I only copied and pasted from the tutorial, so please check if the IDs and everything else match your Proxmox machine.

Please modify the file /etc/modules to the following lines:

Code: 
vfio
vfio_iommu_type1
vfio_pci
vfio_virqfd

Then modify /etc/modprobe.d/vfio.conf to:

Code: 
options vfio-pci ids=1002:15e7,1002:1637 disable=vga
softdep amdgpu pre: vfio-pci
softdep snd_hda_intel pre: vfio-pci

Then you need to post the VM configuration where you want to set up the passthrough.


Then I will need the following outputs:

Code: 
ls -l /etc/modprobe.d/
cat /etc/modprobe.d/pve-blacklist.conf
lspci -nnk   from Proxmox  (only the section with VGA compatible controller AMD and Audio device [AMD/ATI])
lspci -nnk  from your VM (only the section with VGA compatible controller AMD and Audio device [AMD/ATI])
 
Last edited:
You must log in or register to reply here.
Top Bottom