Quadro K600 - Error 43

J

jdnation

New Member
Sep 21, 2025
8
0
1
Hi everyone, Right now I'm struggling trying to assign an Nvidia Quadro K600 to a Windows 10 virtual machine>

I manage to make all configuration in proxmox in order to passthrough the graphic card and the virtual machine recognize the card but there no way to get rid of error 43.

I'm using Proxmox PVE 8.4.14 on a HP Workstation Z400 with Intel Xeon X5675 Processor and with only one gpu card (Quadro K600). I really don't know if is even possible considering my hardware I've read that you need two graphics cards but also I've that is possible with only one card.

this is my .conf file

Code: 
agent: 1
args: -cpu 'host,hv_time,kvm=off,hv_vendor_id=1234567890ab'
boot: order=scsi0;ide2;ide0;net0
cores: 6
cpu: host,hidden=1,flags=+pcid
hostpci0: 0000:28:00.0,pcie=1,romfile=155387.rom
ide0: vm-data:iso/virtio-win-0.1.271.iso,media=cdrom,size=709474K
machine: pc-q35-9.2+pve1
memory: 12288
meta: creation-qemu=9.2.0,ctime=1757364905
name: GPU
net0: virtio=BC:24:11:86:C6:00,bridge=vmbr0,firewall=1
numa: 0
ostype: win10
scsi0: vm-data:104/vm-104-disk-0.raw,backup=0,cache=writeback,iothread=1,replicate=0,size=45G
scsihw: virtio-scsi-single
smbios1: uuid=a143ee45-c03f-4c5f-b8ef-5c9a57a70b37
sockets: 1
tpmstate0: vm-data:104/vm-104-disk-1.raw,size=4M,version=v2.0
vga: std
vmgenid: 0fd78cd4-5742-4b7b-8cd2-6440d3a64daf

Hope somebody could helpme out. Thanks!
 
jdnation said:
I really don't know if is even possible considering my hardware I've read that you need two graphics cards but also I've that is possible with only one card.
Click to expand...
It is possible, but two GPUs are better because at the moment your VM starts, GPU disappears on host and you lose output for proxmox console. For debugging that is not the best situation to start with.

Anyway...you have error43 with Nvidia-drivers that got sucked in by win-updates automatically or did you download and install the whole package from nvidia.com ?

hostpci0: 0000:28:00.0,pcie=1,romfile=155387.rom <- the romfile is only necessary in exceptional cases
 
mr44er said:
It is possible, but two GPUs are better because at the moment your VM starts, GPU disappears on host and you lose output for proxmox console. For debugging that is not the best situation to start with.

Anyway...you have error43 with Nvidia-drivers that got sucked in by win-updates automatically or did you download and install the whole package from nvidia.com ?

hostpci0: 0000:28:00.0,pcie=1,romfile=155387.rom <- the romfile is only necessary in exceptional cases
Click to expand...

Well, I usually manage the proxmox server from the webui, so losing the video output is not a problem for now.

I download the whole package from nvidia.com

Regarding the file. I've tried with and without and the problem persist.
 
Last edited:
Bildschirmfoto zu 2025-09-21 19-49-48.png
Add it this way, works 100% and worked in the past for Windows in VM (at the moment this VM doesn't run Windows).


Edit, there is some more help, but shouldn't be necessary:
T

[SOLVED] Thread 'GPU PASSTHROUGH ( Error 43 while there is output from the gpu's hdmi )'

Hello,

I am new on the proxmox.
I am trying to make gpu passthrough on a windows 10 vm.

I followed many guides like :
--> https://www.reddit.com/r/homelab/comments/b5xpua/the_ultimate_beginners_guide_to_gpu_passthrough/
--> https://pve.proxmox.com/wiki/Pci_passthrough

I am thinking that I am in a good way because in device manager of windows10 vm I can see the graphic card.
Also, I can see the windows home screen in my monitor.

The problem is that i got error43 in device manager.

I install the nvidia drivers with geforce experience.
**If i disable the device and enable...
 
Last edited:
I tried all that and still got the same result. Code 43. Perhaps the graphics card is too old? or the motherboard?
 
jdnation said:
too old? or the motherboard?
Click to expand...
Do you have the latest firmware for this mainboard? If not, flash it first, then reset it and try with defaults but switch on IOMMU and SVM if this off by default. Which exact CPU model is it?

How do the IOMMU-groups look on proxmox? Have you tried blacklisting nvidia-driver on host first?
 
mr44er said:
Do you have the latest firmware for this mainboard? If not, flash it first, then reset it and try with defaults but switch on IOMMU and SVM if this off by default. Which exact CPU model is it?

How do the IOMMU-groups look on proxmox? Have you tried blacklisting nvidia-driver on host first?
Click to expand...

Below IOMMU-groups. 0000:28:00 is the NVIDIA card

Code: 
/sys/kernel/iommu_groups/0/devices/0000:00:00.0
/sys/kernel/iommu_groups/10/devices/0000:00:1a.0
/sys/kernel/iommu_groups/10/devices/0000:00:1a.1
/sys/kernel/iommu_groups/10/devices/0000:00:1a.2
/sys/kernel/iommu_groups/10/devices/0000:00:1a.7
/sys/kernel/iommu_groups/11/devices/0000:00:1b.0
/sys/kernel/iommu_groups/12/devices/0000:00:1c.0
/sys/kernel/iommu_groups/12/devices/0000:00:1c.5
/sys/kernel/iommu_groups/12/devices/0000:01:00.0
/sys/kernel/iommu_groups/13/devices/0000:00:1d.0
/sys/kernel/iommu_groups/13/devices/0000:00:1d.1
/sys/kernel/iommu_groups/13/devices/0000:00:1d.2
/sys/kernel/iommu_groups/13/devices/0000:00:1d.7
/sys/kernel/iommu_groups/14/devices/0000:00:1e.0
/sys/kernel/iommu_groups/14/devices/0000:37:05.0
/sys/kernel/iommu_groups/15/devices/0000:00:1f.0
/sys/kernel/iommu_groups/15/devices/0000:00:1f.2
/sys/kernel/iommu_groups/16/devices/0000:28:00.0
/sys/kernel/iommu_groups/16/devices/0000:28:00.1
/sys/kernel/iommu_groups/17/devices/0000:3f:00.0
/sys/kernel/iommu_groups/17/devices/0000:3f:00.1
/sys/kernel/iommu_groups/18/devices/0000:3f:02.0
/sys/kernel/iommu_groups/18/devices/0000:3f:02.1
/sys/kernel/iommu_groups/18/devices/0000:3f:02.2
/sys/kernel/iommu_groups/18/devices/0000:3f:02.3
/sys/kernel/iommu_groups/18/devices/0000:3f:02.4
/sys/kernel/iommu_groups/18/devices/0000:3f:02.5
/sys/kernel/iommu_groups/19/devices/0000:3f:03.0
/sys/kernel/iommu_groups/19/devices/0000:3f:03.1
/sys/kernel/iommu_groups/19/devices/0000:3f:03.2
/sys/kernel/iommu_groups/19/devices/0000:3f:03.4
/sys/kernel/iommu_groups/1/devices/0000:00:01.0
/sys/kernel/iommu_groups/20/devices/0000:3f:04.0
/sys/kernel/iommu_groups/20/devices/0000:3f:04.1
/sys/kernel/iommu_groups/20/devices/0000:3f:04.2
/sys/kernel/iommu_groups/20/devices/0000:3f:04.3
/sys/kernel/iommu_groups/21/devices/0000:3f:05.0
/sys/kernel/iommu_groups/21/devices/0000:3f:05.1
/sys/kernel/iommu_groups/21/devices/0000:3f:05.2
/sys/kernel/iommu_groups/21/devices/0000:3f:05.3
/sys/kernel/iommu_groups/22/devices/0000:3f:06.0
/sys/kernel/iommu_groups/22/devices/0000:3f:06.1
/sys/kernel/iommu_groups/22/devices/0000:3f:06.2
/sys/kernel/iommu_groups/22/devices/0000:3f:06.3
/sys/kernel/iommu_groups/2/devices/0000:00:03.0
/sys/kernel/iommu_groups/3/devices/0000:00:07.0
/sys/kernel/iommu_groups/4/devices/0000:00:10.0
/sys/kernel/iommu_groups/4/devices/0000:00:10.1
/sys/kernel/iommu_groups/5/devices/0000:00:11.0
/sys/kernel/iommu_groups/5/devices/0000:00:11.1
/sys/kernel/iommu_groups/6/devices/0000:00:14.0
/sys/kernel/iommu_groups/7/devices/0000:00:14.1
/sys/kernel/iommu_groups/8/devices/0000:00:14.2
/sys/kernel/iommu_groups/9/devices/0000:00:15.0

Below blacklist.conf
Code: 
cat /etc/modprobe.d/blacklist.conf
blacklist radeon
blacklist nouveau
blacklist nvidia
 
jdnation said:
hostpci0: 0000:28:00.0,pcie=1,romfile=155387.rom
Click to expand...

It appears to be passing through only part of the device.

Code: 
Only 0
hostpci0: 0000:28:00.0,pcie=1

All Functions
hostpci0: 0000:28:00,pcie=1

The items shown in this image.
It is not configured this way.

mr44er

Post in thread 'Quadro K600 - Error 43'

Bildschirmfoto zu 2025-09-21 19-49-48.png
Add it this way, works 100% and worked in the past for Windows in VM (at the moment this VM doesn't run Windows).


Edit, there is some more help, but shouldn't be necessary:

I previously used an RTX A2000, but I had checked “all functions” without specifying any ROM.
 
Last edited:
uzumo said:
It appears to be passing through only part of the device.

Code: 
Only 0
hostpci0: 0000:28:00.0,pcie=1

All Functions
hostpci0: 0000:28:00,pcie=1

The items shown in this image.
It is not configured this way.

mr44er

Post in thread 'Quadro K600 - Error 43'

Bildschirmfoto zu 2025-09-21 19-49-48.png
Add it this way, works 100% and worked in the past for Windows in VM (at the moment this VM doesn't run Windows).


Edit, there is some more help, but shouldn't be necessary:

I previously used an RTX A2000, but I had checked “all functions” without specifying any ROM.
Click to expand...
you're right and I tried that too, but with no success. See mi .conf right now. (text after # are commands that I've tried in the past is just for me to know what I´ve tried and not repeat again and again

Code: 
#args: -cpu 'host,+kvm_pv_unhalt,+kvm_pv_eoi,hv_vendor_id=NV43FIX,kvm=off'
args: -machine max-ram-below-4g=1G,kernel_irqchip=on
balloon: 0
bios: ovmf
boot: order=scsi0;ide2;ide0;net0
cores: 4

cpu: host
#,hidden=1,flags=+pcid

efidisk0: vm-data:104/vm-104-disk-0.raw,efitype=4m,pre-enrolled-keys=1,size=528K

hostpci0: 0000:28:00,pcie=1
#,romfile=Quadrok600.rom


ide0: vm-data:iso/virtio-win-0.1.271.iso,media=cdrom,size=709474K
ide2: vm-data:iso/W10X64.10in1.ENU.SEP2020_Downloadly.ir.ISO,media=cdrom,size=5831648K
machine: pc-q35-9.2+pve1
memory: 12288
meta: creation-qemu=9.2.0,ctime=1758729233
name: GPU
net0: virtio=BC:24:11:43:04:FC,bridge=vmbr0,firewall=1
numa: 0
ostype: win10
scsi0: vm-data:104/vm-104-disk-1.raw,backup=0,cache=writeback,iothread=1,replicate=0,size=100G
scsihw: virtio-scsi-single
smbios1: uuid=69d387e2-567d-42f8-9f4e-a3f254932d4c
sockets: 1
vga: none
vmgenid: aa46e7ed-f7a6-4582-8048-e86f0c73952e
 
https://forums.unraid.net/topic/120202-code-43-with-gpu-passthrough-on-my-windows-11-vm/#

->

Shan​

April 19, 2023
I was trying all these settings with my hdmi cable plugged in. I unplugged my HDMI cable and the code 43 went away and it's working fine and I'm getting the output to my monitor as soon as I plug the hdmi cable back in. But after I restart leaving the hdmi cabled plugged code 43 comes back.
Click to expand...

Maybe? Is there DP on the card? Sometimes the connectors behave differently.
 
You must log in or register to reply here.
Top Bottom