ryzen-7000-series-proxmox icon indicating copy to clipboard operation
ryzen-7000-series-proxmox copied to clipboard

pve crash on step 7 on "Configuring the GPU in the Windows VM"

Open uppsju opened this issue 2 months ago • 5 comments

Hi, trying this guide on an Aoostar WTR Max running PVE 9.0.6.

All steps up until step 7 on Configuring the GPU in the Windows VM works fine. One difference is my PCI IDs: 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Phoenix3 [1002:1900] (rev d5) 01:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Radeon High Definition Audio Controller [Rembrandt/Strix] [1002:1640]

VM config looks like: ` args: -cpu 'host,-hypervisor,kvm=off'

agent: 1 boot: order=scsi0;ide2;ide0;net0 cores: 2 cpu: host hostpci0: 0000:01:00.0,pcie=1,romfile=vbios_7xxx.bin hostpci1: 0000:01:00.1,pcie=1 ide0: data_rpool:iso/virtio-win-0.1.271.iso,media=cdrom,size=709474K ide2: data_rpool:iso/Win10_22H2_EnglishInternational_x64v1.iso,media=cdrom,size=5991830K machine: pc-q35-10.0 memory: 16384 meta: creation-qemu=10.0.2,ctime=1757336550 name: wintest net0: e1000=BC:24:11:44:BF:56,bridge=vmbr1,firewall=1 numa: 0 ostype: win10 scsi0: rpool_data:vm-100-disk-0,discard=on,iothread=1,size=64G,ssd=1 scsihw: virtio-scsi-single smbios1: uuid=0b3556e8-f7ae-486d-8013-a1662b6475ca sockets: 1 vmgenid: a73d4150-becd-416e-975f-2e59f3fcd4b2 ` When starting the VM, this completely locks up the PVE node, and hard reboot is necessary to revive the system. Are there any obvious mistakes that I've made? Super guide to follow, so thanks for that!

uppsju avatar Sep 08 '25 13:09 uppsju

https://github.com/isc30/ryzen-gpu-passthrough-proxmox/issues/112#issuecomment-2869638903

this worked for me on aoostar gem 12 but need to reboot host to restart vm again

pve-noob avatar Sep 11 '25 07:09 pve-noob

Thanks! The VM doesn't start if I have all four devices added. If I only have the first device enabled I get GPU passthrough. I checked that the host PCI devices match what was in the #112 comment

`hostpci0: 0000:01:00.0,pcie=1,romfile=vbios_7xxx.bin

hostpci1: 0000:01:00.1,pcie=1,romfile=AMDGopDriver.rom hostpci2: 0000:01:00.5,pcie=1 hostpci3: 0000:01:00.6,pcie=1`

uppsju avatar Sep 11 '25 15:09 uppsju

Ok, I see where I needed to make a change. All four hostpci devices must be added to the vfio.conf, in step 4 on "Configuring the GPU for passthrough", in my case:

echo "options vfio-pci ids=1002:1900,1002:1640,1022:15e2,1022:15e3" >> /etc/modprobe.d/vfio.conf

Windows does not appear to communicate then with the "AMD Audio Coprocessor", I'll have to do some more testing.

uppsju avatar Sep 12 '25 16:09 uppsju

@uppsju Did you manage to get it to work on the Aoostar WTR Max?. I'm stuck with a dmesg message whenever I start a device with the GPU [188466.841056] vfio-pci 0000:01:00.0: Firmware has requested this device have a 1:1 IOMMU mapping, rejecting configuring the device without a 1:1 mapping. Contact your platform vendor.

marcelrv avatar Oct 24 '25 20:10 marcelrv

I ended up just not using the AMD Audio Coprocessor feature. These are the devices added on my VM in PVE:

Image

In Windows Device Manager, these are the devices I currently see:

Image

uppsju avatar Oct 24 '25 20:10 uppsju