qemu exited with code 1 - GPU passthrough attemp

wawariors

New Member
Jul 14, 2023
2
0
1
Hello,
I've been trying different solutions for my GPU passthrough to work, but my VM with the PCI passthrough doesn't start. The only error in the CLI is start failed: QEMU exited with code 1
The GPU used is an Nvidia Quadro P400
I've followed and tried solutions in the following places:
https://pve.proxmox.com/pve-docs/pve-admin-guide.html#qm_pci_passthrough
https://pve.proxmox.com/wiki/PCI_Passthrough
https://pve.proxmox.com/wiki/PCI(e)_Passthrough
and passed through a lot of forum posts online, but I can't seem to find a solution.
Here is the syslog for the VM start:
Jul 14 21:29:12 pve pvedaemon[3771]: <root@pam> starting task UPID:pve:000311D9:00027544:64B1A208:qmstart:109:root@pam:
Jul 14 21:29:12 pve pvedaemon[201177]: start VM 109: UPID:pve:000311D9:00027544:64B1A208:qmstart:109:root@pam:
Jul 14 21:29:12 pve systemd[1]: Started 109.scope.
Jul 14 21:29:12 pve kernel: device tap109i0 entered promiscuous mode
Jul 14 21:29:12 pve kernel: fwbr109i0: port 1(fwln109i0) entered disabled state
Jul 14 21:29:12 pve kernel: vmbr0: port 10(fwpr109p0) entered disabled state
Jul 14 21:29:12 pve kernel: device fwln109i0 left promiscuous mode
Jul 14 21:29:12 pve kernel: fwbr109i0: port 1(fwln109i0) entered disabled state
Jul 14 21:29:12 pve kernel: device fwpr109p0 left promiscuous mode
Jul 14 21:29:12 pve kernel: vmbr0: port 10(fwpr109p0) entered disabled state
Jul 14 21:29:13 pve kernel: vmbr0: port 10(fwpr109p0) entered blocking state
Jul 14 21:29:13 pve kernel: vmbr0: port 10(fwpr109p0) entered disabled state
Jul 14 21:29:13 pve kernel: device fwpr109p0 entered promiscuous mode
Jul 14 21:29:13 pve kernel: vmbr0: port 10(fwpr109p0) entered blocking state
Jul 14 21:29:13 pve kernel: vmbr0: port 10(fwpr109p0) entered forwarding state
Jul 14 21:29:13 pve kernel: fwbr109i0: port 1(fwln109i0) entered blocking state
Jul 14 21:29:13 pve kernel: fwbr109i0: port 1(fwln109i0) entered disabled state
Jul 14 21:29:13 pve kernel: device fwln109i0 entered promiscuous mode
Jul 14 21:29:13 pve kernel: fwbr109i0: port 1(fwln109i0) entered blocking state
Jul 14 21:29:13 pve kernel: fwbr109i0: port 1(fwln109i0) entered forwarding state
Jul 14 21:29:13 pve kernel: fwbr109i0: port 2(tap109i0) entered blocking state
Jul 14 21:29:13 pve kernel: fwbr109i0: port 2(tap109i0) entered disabled state
Jul 14 21:29:13 pve kernel: fwbr109i0: port 2(tap109i0) entered blocking state
Jul 14 21:29:13 pve kernel: fwbr109i0: port 2(tap109i0) entered forwarding state
Jul 14 21:29:15 pve kernel: vfio-pci 0000:81:00.0: vfio_ecap_init: hiding ecap 0x19@0x900
Jul 14 21:29:15 pve kernel: kvm[201211]: segfault at b8 ip 000055ef918a8805 sp 00007fff7d242f10 error 4 in qemu-system-x86_64[55ef914fb000+613000] likely on CPU 1 (core 1, socket 0)
Jul 14 21:29:15 pve kernel: Code: 48 85 c0 75 f0 48 8b 6b 60 48 89 b3 80 00 00 00 e8 20 6b 00 00 48 8b 7b 40 83 05 c1 1f b1 00 01 48 85 ff 74 05 e8 cb e7 09 00 <48> 8b 85 b8 00 00 00 48 85 c0 74 7f 8b 93 b0 00 00 00 eb 13 0f 1f
Jul 14 21:29:16 pve kernel: fwbr109i0: port 2(tap109i0) entered disabled state
Jul 14 21:29:16 pve kernel: fwbr109i0: port 2(tap109i0) entered disabled state
Jul 14 21:29:16 pve pvestatd[3670]: VM 109 qmp command failed - VM 109 qmp command 'query-proxmox-support' failed - client closed connection
Jul 14 21:29:16 pve pvedaemon[201177]: start failed: QEMU exited with code 1
Jul 14 21:29:16 pve pvedaemon[3771]: <root@pam> end task UPID:pve:000311D9:00027544:64B1A208:qmstart:109:root@pam: start failed: QEMU exited with code 1
Jul 14 21:29:16 pve systemd[1]: 109.scope: Deactivated successfully.
Jul 14 21:29:16 pve systemd[1]: 109.scope: Consumed 3.346s CPU time.


What other informations should I give to help troubleshoot my problem ?
I hope you have a great day,
wawariors
 
Here is my VM config:
bios: ovmf
boot: order=scsi0;ide2;net0
cores: 2
cpu: x86-64-v2-AES
efidisk0: local-zfs:vm-109-disk-0,efitype=4m,pre-enrolled-keys=1,size=1M
ide2: local:iso/Win10_22H2_English_x64.iso,media=cdrom,size=5971862K
machine: q35
memory: 8192
meta: creation-qemu=8.0.2,ctime=1689361481
name: test
net0: virtio=7A:BB:39:68:4A:45,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
scsi0: local-zfs:vm-109-disk-1,iothread=1,size=100G,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=22b9279f-9f1b-45d2-8234-a9d6aee2de91
sockets: 2
vmgenid: 1e5fce5c-2e17-49bb-8a81-c1326d974471
hostpci0: 81:00,x-vga=1
 

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!