AMD core display pass-through, install win10 does not start

[vrsaoc]

Can anyone help me, I am using AMD5600g core display pass-through, and the installation of win10 does not start and keeps reporting an error, what is the reason?

swtpm_setup: Not overwriting existing state file.
TASK ERROR: start failed: command '/usr/bin/kvm -id 100 -name win10 -no-shutdown -chardev 'socket,id=qmp,path=/var/run/qemu-server/100.qmp,server=on,wait=off' -mon 'chardev=qmp,mode=control' -chardev 'socket,id=qmp-event,path=/var/run/qmeventd.sock,reconnect=5' -mon 'chardev=qmp-event,mode=control' -pidfile /var/run/qemu-server/100.pid -daemonize -smbios 'type=1,uuid=9286a924-8435-460e-89a0-0d29c7e5ee86' -drive 'if=pflash,unit=0,format=raw,readonly=on,file=/usr/share/pve-edk2-firmware//OVMF_CODE_4M.secboot.fd' -drive 'if=pflash,unit=1,format=raw,id=drive-efidisk0,size=540672,file=/dev/pve/vm-100-disk-1' -smp '6,sockets=1,cores=6,maxcpus=6' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vnc 'unix:/var/run/qemu-server/100.vnc,password=on' -no-hpet -cpu 'host,hv_ipi,hv_relaxed,hv_reset,hv_runtime,hv_spinlocks=0x1fff,hv_stimer,hv_synic,hv_time,hv_vapic,hv_vpindex,+kvm_pv_eoi,+kvm_pv_unhalt' -m 4096 -readconfig /usr/share/qemu-server/pve-q35-4.0.cfg -device 'vmgenid,guid=554eacdf-0e67-4daa-b07b-82462d057e00' -device 'usb-tablet,id=tablet,bus=ehci.0,port=1' -device 'vfio-pci,host=0000:06:00.0,id=hostpci0.0,bus=ich9-pcie-port-1,addr=0x0.0,multifunction=on' -device 'vfio-pci,host=0000:06:00.1,id=hostpci0.1,bus=ich9-pcie-port-1,addr=0x0.1' -device 'vfio-pci,host=0000:06:00.2,id=hostpci0.2,bus=ich9-pcie-port-1,addr=0x0.2' -device 'vfio-pci,host=0000:06:00.3,id=hostpci0.3,bus=ich9-pcie-port-1,addr=0x0.3' -device 'vfio-pci,host=0000:06:00.4,id=hostpci0.4,bus=ich9-pcie-port-1,addr=0x0.4' -device 'vfio-pci,host=0000:06:00.6,id=hostpci0.5,bus=ich9-pcie-port-1,addr=0x0.5' -chardev 'socket,id=tpmchar,path=/var/run/qemu-server/100.swtpm' -tpmdev 'emulator,id=tpmdev,chardev=tpmchar' -device 'tpm-tis,tpmdev=tpmdev' -device 'VGA,id=vga,bus=pcie.0,addr=0x1' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:128a4acf23a2' -drive 'file=/var/lib/vz/template/iso/Windows10.iso,if=none,id=drive-ide2,media=cdrom,aio=io_uring' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=101' -device 'ahci,id=ahci0,multifunction=on,bus=pci.0,addr=0x7' -drive 'file=/dev/pve/vm-100-disk-0,if=none,id=drive-sata0,format=raw,cache=none,aio=io_uring,detect-zeroes=on' -device 'ide-hd,bus=ahci0.0,drive=drive-sata0,id=sata0,bootindex=100' -drive 'file=/var/lib/vz/template/iso/virtio-win-0.1.215.iso,if=none,id=drive-sata1,media=cdrom,aio=io_uring' -device 'ide-cd,bus=ahci0.1,drive=drive-sata1,id=sata1,bootindex=103' -netdev 'type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=5A:0D:D3:47:AA:58,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=102' -rtc 'driftfix=slew,base=localtime' -machine 'type=pc-q35-6.1+pve0' -global 'kvm-pit.lost_tick_policy=discard'' failed: got timeout

 

[oguz]

hi,

can you post the VM configuration? qm config VMID

I am using AMD5600g core display pass-through

how are you doing that? can you post the relevant config files you've edited?

and just in case also please send pveversion -v output

 

[vrsaoc]

你好，

你可以发布VM配置吗？qm 配置VMID


您是怎么做到的？您可以发布您编辑的相关配置文件吗？

以防万一，请发送 pveversion -v 输出

OK

400 Parameter verification failed.
vmid: type check ('integer') failed - got 'VMID'
qm config <vmid> [OPTIONS]
root@pve:~# pveversion -v
proxmox-ve: 7.1-1 (running kernel: 5.13.19-2-pve)
pve-manager: 7.1-7 (running version: 7.1-7/df5740ad)
pve-kernel-helper: 7.1-6
pve-kernel-5.13: 7.1-5
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph-fuse: 15.2.15-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-14
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.0-4
libpve-storage-perl: 7.0-15
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.1.2-1
proxmox-backup-file-restore: 2.1.2-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-4
pve-cluster: 7.1-2
pve-container: 4.1-2
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-3
pve-ha-manager: 3.3-1
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.0-3
pve-xtermjs: 4.12.0-1
qemu-server: 7.1-4
smartmontools: 7.2-1
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.1-pve3

root@pve:~# qm config VMID
400 Parameter verification failed.
vmid: type check ('integer') failed - got 'VMID'
qm config <vmid> [OPTIONS]

 

[oguz]

qm config VMID

yeah you need to change that VMID bit with the ID of your VM

 

[vrsaoc]

yeah you need to change that VMID bit with the ID of your VM

yeah you need to change that VMID bit with the ID of your VM

Hello, I am using this for the first time, can you help me how to debug it? I mounted the AMD core display virtual machine and can't start it, but canceling the AMD core display virtual machine can start, why is that?

 

[oguz]

please post the output of the command. you need to change VMID with the number of your VM and run that command to show us your configuration.
like if your VM number is 100, then you do qm config 100

 

[vrsaoc]

please post the output of the command. you need to change VMID with the number of your VM and run that command to show us your configuration.
like if your VM number is 100, then you do qm config 100

bios: ovmf
boot: order=sata0;ide2;net0;sata1
cores: 6
cpu: host
efidisk0: local-lvm:vm-100-disk-1,efitype=4m,pre-enrolled-keys=1,size=4M
ide2: local:iso/Windows10.iso,media=cdrom
machine: pc-q35-6.1
memory: 4096
meta: creation-qemu=6.1.0,ctime=1643026447
name: win10
net0: virtio=5A:0D:D3:47:AA:58,bridge=vmbr0,firewall=1
numa: 0
ostype: win11
sata0: local-lvm:vm-100-disk-0,size=50G
sata1: local:iso/virtio-win-0.1.215.iso,media=cdrom,size=528322K
scsihw: virtio-scsi-pci
smbios1: uuid=9286a924-8435-460e-89a0-0d29c7e5ee86
sockets: 1
tpmstate0: local-lvm:vm-100-disk-2,size=4M,version=v2.0
vmgenid: 554eacdf-0e67-4daa-b07b-82462d057e00

 

[Emilien]

You was able to install Windows 10 with this vm config?

 

[vrsaoc]

You was able to install Windows 10 with this vm config?

Yes, but you can't call AMD's core graphics

 

[oguz]

but didn't you say:

installation of win10 does not start

so i'm confused now... do you mean it works/installs normally without the passthrough?
also have you checked the best practices guide? [0]

it would be also interesting to see the journal from your system when you try to start the VM with the passthrough.

[0]: https://pve.proxmox.com/wiki/Windows_10_guest_best_practices

 

[vrsaoc]

but didn't you say:


so i'm confused now... do you mean it works/installs normally without the passthrough?
also have you checked the best practices guide? [0]

it would be also interesting to see the journal from your system when you try to start the VM with the passthrough.

[0]: https://pve.proxmox.com/wiki/Windows_10_guest_best_practices

Yes, without pass-through AMD core display can start normally

 

[vrsaoc]

I don't know the reason, I can't start the virtual machine if I select the AMD core display, but I can start it without selecting the core display. Could it be a compatibility reason?

 

[Emilien]

After you try to boot the VM with attached the AMD core display, can you post the output of:
tail -n 200 /var/log/syslog

 

[vrsaoc]

After you try to boot the VM with attached the AMD core display, can you post the output of:
tail -n 200 /var/log/syslog

can, the display is waiting for nuclear display, did I not cancel the occupancy of nuclear display?

root@pve:~# tail -n 200 /var/log/syslog

Jan 27 18:50:00 pve kernel: [  514.580205] vfio-pci 0000:06:00.0: vfio_ecap_init: hiding ecap 0xffff@0xffc
Jan 27 18:50:00 pve kernel: [  514.580205] vfio-pci 0000:06:00.0: vfio_ecap_init: hiding ecap 0xffff@0xffc
Jan 27 18:50:00 pve kernel: [  514.580206] vfio-pci 0000:06:00.0: vfio_ecap_init: hiding ecap 0xffff@0xffc
Jan 27 18:50:00 pve kernel: [  514.580207] vfio-pci 0000:06:00.0: vfio_ecap_init: hiding ecap 0xffff@0xffc
Jan 27 18:50:00 pve kernel: [  514.580208] vfio-pci 0000:06:00.0: vfio_ecap_init: hiding ecap 0xffff@0xffc
Jan 27 18:50:00 pve kernel: [  514.580209] vfio-pci 0000:06:00.0: vfio_ecap_init: hiding ecap 0xffff@0xffc
Jan 27 18:50:00 pve kernel: [  514.580647] vfio-pci 0000:06:00.0: BAR 0: can't reserve [mem 0xd0000000-0xdfffffff 64bit pref]
Jan 27 18:50:00 pve kernel: [  514.642127] fwbr100i0: port 2(tap100i0) entered disabled state
Jan 27 18:50:00 pve kernel: [  514.642218] fwbr100i0: port 2(tap100i0) entered disabled state
Jan 27 18:50:00 pve kernel: [  514.703084] vfio-pci 0000:06:00.0: can't change power state from D3cold to D0 (config space inaccessible)
Jan 27 18:50:01 pve kernel: [  515.734842] vfio-pci 0000:06:00.1: can't change power state from D0 to D3hot (config space inaccessible)
Jan 27 18:50:01 pve kernel: [  515.734865] vfio-pci 0000:06:00.2: can't change power state from D0 to D3hot (config space inaccessible)
Jan 27 18:50:01 pve kernel: [  515.735486] vfio-pci 0000:06:00.3: can't change power state from D0 to D3hot (config space inaccessible)
Jan 27 18:50:01 pve kernel: [  515.736106] vfio-pci 0000:06:00.4: can't change power state from D0 to D3hot (config space inaccessible)
Jan 27 18:50:01 pve kernel: [  515.736124] vfio-pci 0000:06:00.6: can't change power state from D0 to D3hot (config space inaccessible)
Jan 27 18:50:31 pve kernel: [  545.737295]
Jan 27 18:50:31 pve kernel: [  545.737297]
Jan 27 18:50:31 pve kernel: [  545.737297] Initialized Local Variables for Method [M277]:
Jan 27 18:50:31 pve kernel: [  545.737298]   Local0: 00000000dabc4bbd <Obj>           Integer 0000000000000006
Jan 27 18:50:31 pve kernel: [  545.737303]   Local1: 00000000855f22c5 <Obj>           Integer 0000000015E21022
Jan 27 18:50:31 pve kernel: [  545.737305]   Local4: 000000005f64f82a <Obj>           Integer 0000000000000000
Jan 27 18:50:31 pve kernel: [  545.737308]
Jan 27 18:50:31 pve kernel: [  545.737308] No Arguments are initialized for method [M277]
Jan 27 18:50:31 pve kernel: [  545.737309]
Jan 27 18:50:31 pve kernel: [  545.737310] ACPI Error: Aborting method \M277 due to previous error (AE_AML_LOOP_TIMEOUT) (20210331/psparse-529)
Jan 27 18:50:31 pve kernel: [  545.737340] ACPI Error: Aborting method \_SB.PCI0.GP17.AZAL._PS3 due to previous error (AE_AML_LOOP_TIMEOUT) (20210331/psparse-529)
Jan 27 18:50:31 pve kernel: [  545.737368] acpi device:19: Failed to change power state to D3hot
Jan 27 18:50:31 pve kernel: [  545.737371] vfio-pci 0000:06:00.0: invalid power transition (from D3cold to D3hot)
Jan 27 18:50:31 pve systemd[1]: 100.scope: Succeeded.
Jan 27 18:50:31 pve systemd[1]: 100.scope: Consumed 30.730s CPU time.
Jan 27 18:56:47 pve pvedaemon[1110]: <root@pam> successful auth for user 'root@pam'
Jan 27 18:56:47 pve systemd[1]: Starting Cleanup of Temporary Directories...
Jan 27 18:56:47 pve systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
Jan 27 18:56:47 pve systemd[1]: Finished Cleanup of Temporary Directories.
Jan 27 19:06:16 pve pveproxy[1119]: worker exit
Jan 27 19:06:16 pve pveproxy[1118]: worker 1119 finished
Jan 27 19:06:16 pve pveproxy[1118]: starting 1 worker(s)
Jan 27 19:06:16 pve pveproxy[1118]: worker 4766 started
Jan 27 19:07:08 pve pvedaemon[1110]: <root@pam> update VM 100: -hostpci1 0000:06:00.0
Jan 27 19:07:14 pve pvedaemon[1110]: <root@pam> update VM 100: -delete hostpci1
Jan 27 19:07:16 pve pvedaemon[1110]: <root@pam> starting task UPID:pve:00001325:00025DEC:61F27CE4:qmstart:100:root@pam:
Jan 27 19:07:16 pve pvedaemon[4901]: start VM 100: UPID:pve:00001325:00025DEC:61F27CE4:qmstart:100:root@pam:
Jan 27 19:07:16 pve kernel: [ 1550.682631] vfio-pci 0000:06:00.0: can't change power state from D3cold to D0 (config space inaccessible)
Jan 27 19:07:16 pve kernel: [ 1551.426178] vfio-pci 0000:06:00.0: timed out waiting for pending transaction; performing function level reset anyway
Jan 27 19:07:18 pve kernel: [ 1552.674159] vfio-pci 0000:06:00.0: not ready 1023ms after FLR; waiting
Jan 27 19:07:19 pve kernel: [ 1553.730150] vfio-pci 0000:06:00.0: not ready 2047ms after FLR; waiting
Jan 27 19:07:21 pve kernel: [ 1555.970109] vfio-pci 0000:06:00.0: not ready 4095ms after FLR; waiting
Jan 27 19:07:25 pve kernel: [ 1560.322052] vfio-pci 0000:06:00.0: not ready 8191ms after FLR; waiting
Jan 27 19:07:34 pve kernel: [ 1568.769919] vfio-pci 0000:06:00.0: not ready 16383ms after FLR; waiting
Jan 27 19:07:51 pve kernel: [ 1585.665653] vfio-pci 0000:06:00.0: not ready 32767ms after FLR; waiting

 

[Emilien]

Check your:
nano /etc/default/grub
and add these parameters in this line:
GRUB_CMDLINE_LINUX_DEFAULT="quiet amd_iommu=on iommu=pt nomodeset textonly video=vesafb:off video=efifb:off"
than:
update-grub pve-efiboot-tool refresh reboot

 

[vrsaoc]

Check your:
nano /etc/default/grub
and add these parameters in this line:
GRUB_CMDLINE_LINUX_DEFAULT="quiet amd_iommu=on iommu=pt nomodeset textonly video=vesafb:off video=efifb:off"
than:
update-grub pve-efiboot-tool refresh reboot

Sorry, I did, but it still doesn't work

swtpm_setup: Not overwriting existing state file.
TASK ERROR: start failed: command '/usr/bin/kvm -id 100 -name win10 -no-shutdown -chardev 'socket,id=qmp,path=/var/run/qemu-server/100.qmp,server=on,wait=off' -mon 'chardev=qmp,mode=control' -chardev 'socket,id=qmp-event,path=/var/run/qmeventd.sock,reconnect=5' -mon 'chardev=qmp-event,mode=control' -pidfile /var/run/qemu-server/100.pid -daemonize -smbios 'type=1,uuid=9286a924-8435-460e-89a0-0d29c7e5ee86' -drive 'if=pflash,unit=0,format=raw,readonly=on,file=/usr/share/pve-edk2-firmware//OVMF_CODE_4M.secboot.fd' -drive 'if=pflash,unit=1,format=raw,id=drive-efidisk0,size=540672,file=/dev/pve/vm-100-disk-1' -smp '6,sockets=1,cores=6,maxcpus=6' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vnc 'unix:/var/run/qemu-server/100.vnc,password=on' -no-hpet -cpu 'host,hv_ipi,hv_relaxed,hv_reset,hv_runtime,hv_spinlocks=0x1fff,hv_stimer,hv_synic,hv_time,hv_vapic,hv_vpindex,+kvm_pv_eoi,+kvm_pv_unhalt' -m 4096 -readconfig /usr/share/qemu-server/pve-q35-4.0.cfg -device 'vmgenid,guid=554eacdf-0e67-4daa-b07b-82462d057e00' -device 'usb-tablet,id=tablet,bus=ehci.0,port=1' -device 'vfio-pci,host=0000:06:00.0,id=hostpci0,bus=pci.0,addr=0x10' -chardev 'socket,id=tpmchar,path=/var/run/qemu-server/100.swtpm' -tpmdev 'emulator,id=tpmdev,chardev=tpmchar' -device 'tpm-tis,tpmdev=tpmdev' -device 'VGA,id=vga,bus=pcie.0,addr=0x1' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:128a4acf23a2' -device 'ahci,id=ahci0,multifunction=on,bus=pci.0,addr=0x7' -drive 'file=/dev/pve/vm-100-disk-0,if=none,id=drive-sata0,format=raw,cache=none,aio=io_uring,detect-zeroes=on' -device 'ide-hd,bus=ahci0.0,drive=drive-sata0,id=sata0,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=5A:0D:D3:47:AA:58,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=101' -rtc 'driftfix=slew,base=localtime' -machine 'type=pc-q35-6.1+pve0' -global 'kvm-pit.lost_tick_policy=discard'' failed: got timeout

Jan 27 20:41:34 pve kernel: [  797.101504] fwbr100i0: port 2(tap100i0) entered disabled state
Jan 27 20:41:34 pve kernel: [  797.101621] fwbr100i0: port 2(tap100i0) entered disabled state
Jan 27 20:41:34 pve kernel: [  797.174436] vfio-pci 0000:06:00.0: can't change power state from D3cold to D0 (config space inaccessible)
Jan 27 20:41:34 pve pvestatd[1054]: VM 100 qmp command failed - VM 100 not running
Jan 27 20:41:35 pve kernel: [  798.222196] vfio-pci 0000:06:00.1: can't change power state from D0 to D3hot (config space inaccessible)
Jan 27 20:41:35 pve kernel: [  798.222203] vfio-pci 0000:06:00.2: can't change power state from D0 to D3hot (config space inaccessible)
Jan 27 20:41:35 pve kernel: [  798.222808] vfio-pci 0000:06:00.3: can't change power state from D0 to D3hot (config space inaccessible)
Jan 27 20:41:35 pve kernel: [  798.223413] vfio-pci 0000:06:00.4: can't change power state from D0 to D3hot (config space inaccessible)
Jan 27 20:41:35 pve kernel: [  798.223415] vfio-pci 0000:06:00.6: can't change power state from D0 to D3hot (config space inaccessible)
Jan 27 20:42:05 pve kernel: [  828.224893]
Jan 27 20:42:05 pve kernel: [  828.224896]
Jan 27 20:42:05 pve kernel: [  828.224896] Initialized Local Variables for Method [M277]:
Jan 27 20:42:05 pve kernel: [  828.224897]   Local0: 000000005a85dd34 <Obj>           Integer 0000000000000006
Jan 27 20:42:05 pve kernel: [  828.224901]   Local1: 000000006d43a7dc <Obj>           Integer 0000000015E21022
Jan 27 20:42:05 pve kernel: [  828.224904]   Local4: 000000004cc61559 <Obj>           Integer 0000000000000000
Jan 27 20:42:05 pve kernel: [  828.224906]
Jan 27 20:42:05 pve kernel: [  828.224907] No Arguments are initialized for method [M277]
Jan 27 20:42:05 pve kernel: [  828.224907]
Jan 27 20:42:05 pve kernel: [  828.224909] ACPI Error: Aborting method \M277 due to previous error (AE_AML_LOOP_TIMEOUT) (20210331/psparse-529)
Jan 27 20:42:05 pve kernel: [  828.224918] ACPI Error: Aborting method \_SB.PCI0.GP17.AZAL._PS3 due to previous error (AE_AML_LOOP_TIMEOUT) (20210331/psparse-529)
Jan 27 20:42:05 pve kernel: [  828.224925] acpi device:19: Failed to change power state to D3hot
Jan 27 20:42:05 pve kernel: [  828.224929] vfio-pci 0000:06:00.0: invalid power transition (from D3cold to D3hot)
Jan 27 20:42:05 pve systemd[1]: 100.scope: Succeeded.
Jan 27 20:42:05 pve systemd[1]: 100.scope: Consumed 30.731s CPU time.
Jan 27 20:43:58 pve systemd[1]: Starting Cleanup of Temporary Directories...
Jan 27 20:43:58 pve systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
Jan 27 20:43:58 pve systemd[1]: Finished Cleanup of Temporary Directories.
Jan 27 20:45:52 pve pvedaemon[1087]: <root@pam> successful auth for user 'root@pam'
Jan 27 20:50:25 pve pvedaemon[4327]: start VM 100: UPID:pve:000010E7:000206F6:61F29511:qmstart:100:root@pam:
Jan 27 20:50:25 pve pvedaemon[1087]: <root@pam> starting task UPID:pve:000010E7:000206F6:61F29511:qmstart:100:root@pam:
Jan 27 20:50:25 pve kernel: [ 1327.899850] vfio-pci 0000:06:00.0: can't change power state from D3cold to D0 (config space inaccessible)
Jan 27 20:50:26 pve kernel: [ 1328.641347] vfio-pci 0000:06:00.0: timed out waiting for pending transaction; performing function level reset anyway
Jan 27 20:50:27 pve kernel: [ 1329.889334] vfio-pci 0000:06:00.0: not ready 1023ms after FLR; waiting
Jan 27 20:50:28 pve kernel: [ 1330.945312] vfio-pci 0000:06:00.0: not ready 2047ms after FLR; waiting
Jan 27 20:50:30 pve kernel: [ 1333.089284] vfio-pci 0000:06:00.0: not ready 4095ms after FLR; waiting
Jan 27 20:50:35 pve kernel: [ 1337.441213] vfio-pci 0000:06:00.0: not ready 8191ms after FLR; waiting
Jan 27 20:50:43 pve kernel: [ 1345.889099] vfio-pci 0000:06:00.0: not ready 16383ms after FLR; waiting
Jan 27 20:51:02 pve kernel: [ 1364.320832] vfio-pci 0000:06:00.0: not ready 32767ms after FLR; waiting

 

[Emilien]

Can you post the output of:
dmesg | grep nomode

 

[vrsaoc]

I tried typing dmesg | grep nomode, but according to the information returned to me, I did not type correctly

root@pve:~# dmesg | grep nomode
root@pve:~#

 

[Emilien]

This confirm that you didn't set properly:
GRUB_CMDLINE_LINUX_DEFAULT="quiet amd_iommu=on iommu=pt nomodeset textonly video=vesafb:off video=efifb:off"

Remember todo all the steps

 

[leesteken]

You can check which kernel parameters are passed using cat /proc/cmdline. It also depends on the bootloader.
Note that amd_iommu=on is not needed (and actually invalid), iommu=pt probably does not what you think it does. And does nomodeset textonly actually do anything when turinng off vesafb and efifb (and maybe blacklisting amdgpu)?
As far as I know, nobody has much luck with passthrough of the built-in GPU of a Ryzen APU but maybe I have just missed it. Can anyone point to a success story on the internet?