Issue booting Windows 10 (GPU Passthrough Edition)

herotm

Member
Jun 15, 2021
13
0
6
36
CPU: AMD 5800X
GPU: AMD 5600XT
Motherboard: Crosshair VIII Hero Wifi ( Latest BIOS )
PVE: 7.4-1
Kernel 6.2.9
4G Above Decoding Off
Resize Bar Off
Boot with Virtio-GPU works
GPU Passthrough boot = problems
AMD Vendor-Reset installed

Issue: Fresh reboot, then turn on Windows 10, Monitor shows Infinite Circle Loop. Stopped VM and turn back on gets hit with Unable to start error on PVE Panel.

kvm: ../hw/pci/pci.c:1562: pci_irq_handler: Assertion `0 <= irq_num && irq_num < PCI_NUM_PINS' failed.
TASK ERROR: start failed: QEMU exited with code 1


dmesg

[ 265.270481] vfio-pci 0000:0d:00.0: vfio_ecap_init: hiding ecap 0xffff@0xffc
[ 265.270482] vfio-pci 0000:0d:00.0: vfio_ecap_init: hiding ecap 0xffff@0xffc
[ 265.270484] vfio-pci 0000:0d:00.0: vfio_ecap_init: hiding ecap 0xffff@0xffc
[ 265.311885] vmbr0: port 2(tap500i0) entered disabled state
[ 265.311993] vmbr0: port 2(tap500i0) entered disabled state
[ 265.411823] vfio-pci 0000:0d:00.0: Unable to change power state from D3cold to D0, device inaccessible
[ 265.414433] vfio-pci 0000:0d:00.1: Unable to change power state from D3cold to D0, device inaccessible
[ 265.416903] vfio-pci 0000:0d:00.0: Unable to change power state from D3cold to D0, device inaccessible
[ 265.418868] vfio-pci 0000:0d:00.1: Unable to change power state from D3cold to D0, device inaccessible
[ 267.467745] pcieport 0000:0c:00.0: Data Link Layer Link Active not set in 1000 msec
[ 267.483427] vfio-pci 0000:0d:00.1: Unable to change power state from D3cold to D0, device inaccessible
[ 267.483442] vfio-pci 0000:0d:00.0: Unable to change power state from D3cold to D0, device inaccessible


vfio.conf

options vfio-pci ids=1002:731f,1002:ab38 disable_vga=1
softdep amdgpu pre: vfio-pci
softdep snd_hda_intel pre: vfio-pci

grub is default with no modifications.

Steps taken:
Deleted VM and Restored, on first boot, loads to windows just alright. After idling for too long screen will not come back. Node reboot and Turn VM back on again causes the above problem.
 

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!