GT710 Passthrough not working but shows up in the device manager.

MR41211

New Member
Sep 11, 2024
6
0
1
I am trying to get a GT 710 for a gpu passthrough to a windows 10 machine. Can someone help me with some of the issues ive had?:
  1. When i start the vm, the gpu has code 43 in device manager, but if i disable, then enable it, device manager will say its working. Even though device manager says its working, it doesnt show up in task manager.
1A. When I plug in a monitor to the gpu, nothing happens
  1. Code 43, which doesnt go away with disabling and enabling again


I've already tried with the latest drivers from nv and suggested drivers from the windows update, but they don't work.


I have
GT 710
Intel i5-2400
Proxmox 8.2.2



args: -cpu 'host,+kvm_pv_unhalt,+kvm_pv_eoi,hv_vendor_id=NV43FIX,-hypervisor,kvm=off'
balloon: 0
bios: ovmf
boot: order=sata0;ide0;ide2;net0
cores: 4
cpu: host,hidden=1,flags=+pcid,
efidisk0: local-lvm:vm-102-disk-0,efitype=4m,pre-enrolled-keys=1,size=4M
hostpci0: mapping=GT710,pcie=1,romfile=MSI.GT710.2048.160112.rom
ide0: local:iso/virtio-win-0.1.262.iso,media=cdrom,size=708140K
ide2: local:iso/Windows.iso,media=cdrom,size=4779200K
machine: pc-q35-8.1,viommu=intel
memory: 4096
meta: creation-qemu=8.1.5,ctime=1726107470
name: ss
net0: e1000e=BC:24:11:1A:D1:98,bridge=vmbr0,firewall=1
numa: 0
ostype: win10
sata0: local-lvm:vm-102-disk-1,discard=on,size=50G
scsihw: virtio-scsi-single
smbios1: uuid=2c40bc51-7f23-4674-9d66-1e923ea61a4b
snaptime: 1726161336
sockets: 1
vmgenid: 3bce1496-db70-49b6-97b3-2938151f3c6e


GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on iommu=pt pcie_acs_override=downstream,multifunction nofb nomodeset video=efifb:eek:ff video=ves>
GRUB_CMDLINE_LINUX=""

vfio
vfio_iommu_type1
vfio_pci
vfio_virqfd

[ 1944.111389] vmbr0: port 2(fwpr102p0) entered blocking state
[ 1944.111392] vmbr0: port 2(fwpr102p0) entered forwarding state
[ 1944.120622] fwbr102i0: port 1(fwln102i0) entered blocking state
[ 1944.120630] fwbr102i0: port 1(fwln102i0) entered disabled state
[ 1944.120652] fwln102i0: entered allmulticast mode
[ 1944.120702] fwln102i0: entered promiscuous mode
[ 1944.120744] fwbr102i0: port 1(fwln102i0) entered blocking state
[ 1944.120746] fwbr102i0: port 1(fwln102i0) entered forwarding state
[ 1944.129352] fwbr102i0: port 2(tap102i0) entered blocking state
[ 1944.129360] fwbr102i0: port 2(tap102i0) entered disabled state
[ 1944.129375] tap102i0: entered allmulticast mode
[ 1944.129440] fwbr102i0: port 2(tap102i0) entered blocking state
[ 1944.129442] fwbr102i0: port 2(tap102i0) entered forwarding state
[ 1944.721907] resource: resource sanity check: requesting [mem 0x00000000000c0000-0x00000000000dffff], which spans more than PCI Bus 0000:00 [mem 0x000d8000-0x000dffff window]
[ 1944.721915] caller pci_map_rom+0x6c/0x1d0 mapping multiple BARs
[ 1944.721922] vfio-pci 0000:01:00.0: No more image in the PCI ROM
 
Last edited:

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!