Error 43 for the umpteenth time!

BICEPS

Active Member
Aug 20, 2019
9
0
41
34
I had been trying to get my Windows 10 VM for 3 days already and I've just about had it - I figured this warrants some help because I've just about exhausted the last of my brain cells! The gist is that I want to passthrough my card to the Windows guest but nothing I do removes this error.

Specs:
  • Supermicro X9DRL-3F
  • 2x E5-2670s
  • 56GB 1333MHz ECC (1 slot is not functional but everything else works perfectly)
  • GTX 950

VM Config
Code:
args: -cpu 'host,-hypervisor,+kvm_pv_unhalt,+kvm_pv_eoi,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_reset,hv_vpindex,hv_runtime,hv_relaxed,kvm=off,hv_vendor_id=proxmoxplz'
bios: ovmf
bootdisk: ide0
cores: 4
cpu: host,hidden=1,flags=+pcid
hostpci0: 05:00,pcie=1,x-vga=1,rombar=1
machine: pc-q35-3.1
memory: 4096
name: Win10
numa: 1
ostype: win10
sockets: 2

lspci -nnkoutput (cut lines out for clarity)
Code:
05:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM206 [GeForce GTX 950] [10de:1402] (rev a1)
        Subsystem: NVIDIA Corporation GM206 [GeForce GTX 950] [10de:11a9]
        Kernel driver in use: vfio-pci
        Kernel modules: nvidiafb, nouveau
05:00.1 Audio device [0403]: NVIDIA Corporation GM206 High Definition Audio Controller [10de:0fba] (rev a1)
        Subsystem: NVIDIA Corporation GM206 High Definition Audio Controller [10de:11a9]
        Kernel driver in use: vfio-pci
        Kernel modules: snd_hda_intel

What I've tried
I have obviously followed the guides on PCIe passthrough from the Proxmox wiki and numerous other guides such as this with no dice. Tried several combinations of pcie on/off with rombar on/off. Moreover, I dumped my vBIOS with GPUz then gave using the romfile a shot. Needless to say that did not work either. I've also tried using this Nvidia KVM patcher some suggested which while it did solve the error 43 message, brought up a code 52 error instead. Whether I compiled it wrong or not, I'm not sure. But I'd rather not go that route if necessary.

In all the modifications, I booted into safe mode and DDU'd the graphics driver every time so existing driver conflicts is very unlikely. I'd also like to add that Windows does not detect that it is a VM based off of task manager as far as I know.

Also, I've added these boot parameters quiet intel_iommu=on video=vesafb:off video=efifb:off inside /etc/default/grub because I had a hunch it had something to do with the host nabbing my card at boot - obviously as no LGA2011 CPUs have internal graphics. Alas, I come to the same conclusion.

All the methods I've tried to remedy this issue still ended up with a code 43 and it's driving me nuts! I'd appreciate it if anyone can offer some advice on what else I could do. I was hoping I wouldn't have to make a thread as it'd make me feel inadequate for not searching the forums hard enough but I seriously have no idea how to continue from here. If there's anything else I can provide I'd be glad to. Thanks in advance to everybody!
 
Not too sure if bumping is frowned upon but I posted this late in the night so it's probably getting overshadowed by newer threads. Bump.
 
i'd try without the args line, and with a second gpu just for the host... when the host boots, it has to put out some graphics and sometimes this is enough to wrongly initialize the card
 

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!