GPU passthrough Win11 code 43 GeForce RTX 3080

DocMAX

Member
Jan 30, 2023
200
14
18
Bremen
It used to work but something happened and i get error code 43 all the time. I tried all kernel switches and configs described in the threats here. No chance,
Does anyone have the same GPU and can share a working setup?
pve-manager/8.0.4/d258a813cfa6b390 (running kernel: 6.2.16-15-pve)
 
Yes of course:
Code:
[Mo Okt 30 10:20:29 2023] device tap300i0 entered promiscuous mode
[Mo Okt 30 10:20:29 2023] vmbr0: port 2(fwpr300p0) entered blocking state
[Mo Okt 30 10:20:29 2023] vmbr0: port 2(fwpr300p0) entered disabled state
[Mo Okt 30 10:20:29 2023] device fwpr300p0 entered promiscuous mode
[Mo Okt 30 10:20:29 2023] vmbr0: port 2(fwpr300p0) entered blocking state
[Mo Okt 30 10:20:29 2023] vmbr0: port 2(fwpr300p0) entered forwarding state
[Mo Okt 30 10:20:29 2023] fwbr300i0: port 1(fwln300i0) entered blocking state
[Mo Okt 30 10:20:29 2023] fwbr300i0: port 1(fwln300i0) entered disabled state
[Mo Okt 30 10:20:29 2023] device fwln300i0 entered promiscuous mode
[Mo Okt 30 10:20:29 2023] fwbr300i0: port 1(fwln300i0) entered blocking state
[Mo Okt 30 10:20:29 2023] fwbr300i0: port 1(fwln300i0) entered forwarding state
[Mo Okt 30 10:20:29 2023] fwbr300i0: port 2(tap300i0) entered blocking state
[Mo Okt 30 10:20:29 2023] fwbr300i0: port 2(tap300i0) entered disabled state
[Mo Okt 30 10:20:29 2023] fwbr300i0: port 2(tap300i0) entered blocking state
[Mo Okt 30 10:20:29 2023] fwbr300i0: port 2(tap300i0) entered forwarding state
[Mo Okt 30 10:20:30 2023] vfio-pci 0000:06:00.0: vfio_ecap_init: hiding ecap 0x1e@0x258
[Mo Okt 30 10:20:30 2023] vfio-pci 0000:06:00.0: vfio_ecap_init: hiding ecap 0x19@0x900
[Mo Okt 30 10:20:30 2023] vfio-pci 0000:06:00.0: vfio_ecap_init: hiding ecap 0x26@0xc1c
[Mo Okt 30 10:20:30 2023] vfio-pci 0000:06:00.0: vfio_ecap_init: hiding ecap 0x27@0xd00
[Mo Okt 30 10:20:30 2023] vfio-pci 0000:06:00.0: vfio_ecap_init: hiding ecap 0x25@0xe00

Also my config:

Code:
args: -cpu 'host,kvm=off,hv_vendor_id=NV43FIX,+hypervisor,+topoext'
bios: ovmf
boot: order=virtio0;ide2;net0;ide0
cores: 32
cpu: host,hidden=1
efidisk0: zpool-nfs:300/vm-300-disk-0.qcow2,efitype=4m,pre-enrolled-keys=1,size=528K
hostpci0: 0000:06:00.0,romfile=vgabios-rtx3080.bin,x-vga=1
hostpci1: 0000:08:00.4
machine: pc-q35-8.0
memory: 8192
meta: creation-qemu=8.0.2,ctime=1698618264
name: win-pt-game
net0: virtio=C6:B7:7C:92:33:BE,bridge=vmbr0,firewall=1
numa: 0
ostype: win11
scsihw: virtio-scsi-single
smbios1: uuid=fe8d8ba6-0f8f-4d71-a21a-269ba7b4b619
sockets: 1
tpmstate0: zpool-nfs:300/vm-300-disk-0.raw,size=4M,version=v2.0
usb0: host=0c45:5004
usb1: host=093a:2533
virtio0: local:300/vm-300-disk-0.qcow2,discard=on,iothread=1,size=128G
vmgenid: 207513b5-ff11-476e-af90-ce0256cf355c
 
Last edited:
Now it's working. I removed "cpu: host,hidden=1" completly and also the args.
What is the CPU Type set to now according to the Proxmox GUI? Is it kvm64 or x86-64-v2?
Why is it working?!?
I think you need to ask NVidia (or maybe Microsoft) that question. What did they change that broke passthrough with Code 43 again? Anyway, glad you got it working.
 
OK, this is crazy... adding host,hidden=1 again is still working... so something else happened which is not understandable. All of the sudden it's working with ANY config.
 

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!