GPU passthrough in Windows 7

mailo95

Member
Sep 17, 2021
15
3
8
Hello,

I have a problem regarding GPU passthrough in Win7. The problem is that if I don't have any GPU machine boots without any issues but if I attach my GTX1060 stuck on loading screen without any errors or CPU activity. I've installed Win7 in UEFI with Secure Boot disabled. Here is my VM cfg:
Code:
balloon: 0
bios: ovmf
boot: order=sata1;sata0
cores: 4
cpu: host,hidden=1
cpulimit: 4
cpuunits: 200
efidisk0: local-lvm:vm-107-disk-0,efitype=4m,pre-enrolled-keys=1,size=4M
hostpci0: 0000:01:00,pcie=1,x-vga=1
hostpci1: 0000:00:1b,pcie=1
hostpci2: 0000:07:00,pcie=1
hostpci3: 0000:08:00,pcie=1
hostpci4: 0000:09:00,pcie=1
hostpci5: 0000:0a:00,pcie=1
machine: pc-q35-9.0
memory: 8192
meta: creation-qemu=9.0.0,ctime=1723464956
name: Win7VM
net0: e1000e=XX:XX:XX:XX:XX:XX,bridge=vmbr1
numa: 0
ostype: win7
sata0: local-lvm:vm-107-disk-1,discard=on,size=100G,ssd=1
sata1: backups:iso/en_windows_7_with_sp1_x64.iso,media=cdrom,size=3243004K
scsihw: lsi
smbios1: uuid=xxxxx-xxxxx-XXXxx-XXxx-xxxx-xxxx,manufacturer=QVNVU1RlSyBDb21wdXRlciBJbmMu,product=UkFNUEFHRSBJViBFWFRSRU1F,family=WDc5,base64=1
sockets: 1
vcpus: 4
vga: none
vmgenid: a92e63e9-29ed-47de-9c5a-eb65fb05d934
vmstatestorage: local-lvm

Code:
/usr/bin/kvm -id 107 -name 'Win7VM,debug-threads=on' -no-shutdown -chardev 'socket,id=qmp,path=/var/run/qemu-server/107.qmp,server=on,wait=off' -mon 'chardev=qmp,mode=control' -chardev 'socket,id=qmp-event,path=/var/run/qmeventd.sock,reconnect=5' -mon 'chardev=qmp-event,mode=control' -pidfile /var/run/qemu-server/107.pid -daemonize -smbios 'type=1,manufacturer=ASUSTeK Computer Inc.,product=RAMPAGE IV EXTREME,uuid=44d42380-5bcb-11d9-a76b-ac220bc9860d,family=X79' -drive 'if=pflash,unit=0,format=raw,readonly=on,file=/usr/share/pve-edk2-firmware//OVMF_CODE_4M.secboot.fd' -drive 'if=pflash,unit=1,id=drive-efidisk0,format=raw,file=/dev/pve/vm-107-disk-0,size=540672' -smp '4,sockets=1,cores=4,maxcpus=4' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vga none -nographic -cpu 'host,kvm=off,+kvm_pv_eoi,+kvm_pv_unhalt' -m 8192 -readconfig /usr/share/qemu-server/pve-q35-4.0.cfg -device 'vmgenid,guid=a92e63e9-29ed-47de-9c5a-eb65fb05d934' -device 'usb-tablet,id=tablet,bus=ehci.0,port=1' -device 'vfio-pci,host=0000:01:00.0,id=hostpci0.0,bus=pcie.0,addr=0x10.0,multifunction=on' -device 'vfio-pci,host=0000:01:00.1,id=hostpci0.1,bus=pcie.0,addr=0x10.1' -device 'vfio-pci,host=0000:00:1b.0,id=hostpci1,bus=pcie.0,addr=0x11' -device 'vfio-pci,host=0000:07:00.0,id=hostpci2,bus=pcie.0,addr=0x12' -device 'vfio-pci,host=0000:08:00.0,id=hostpci3,bus=pcie.0,addr=0x13' -device 'vfio-pci,host=0000:09:00.0,id=hostpci4,bus=pcie.0,addr=0x9' -device 'vfio-pci,host=0000:0a:00.0,id=hostpci5,bus=pcie.0,addr=0xa' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:76f67412b3c9' -device 'ahci,id=ahci0,multifunction=on,bus=pci.0,addr=0x7' -drive 'file=/dev/pve/vm-107-disk-1,if=none,id=drive-sata0,discard=on,format=raw,cache=none,aio=io_uring,detect-zeroes=unmap' -device 'ide-hd,bus=ahci0.0,drive=drive-sata0,id=sata0,rotation_rate=1,bootindex=101' -drive 'file=/mnt/pve/backups/template/iso/en_windows_7_with_sp1_x64.iso,if=none,id=drive-sata1,media=cdrom,aio=io_uring' -device 'ide-cd,bus=ahci0.1,drive=drive-sata1,id=sata1,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap107i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000e,mac=BC:24:11:7F:F8:92,netdev=net0,bus=pci.0,addr=0x12,id=net0' -rtc 'driftfix=slew,base=localtime' -machine 'hpet=off,type=pc-q35-9.0+pve0' -global 'kvm-pit.lost_tick_policy=discard'

Code:
proxmox-ve: 8.2.0 (running kernel: 6.8.8-2-pve)
pve-manager: 8.2.4 (running version: 8.2.4/faa83925c9641325)
proxmox-kernel-helper: 8.1.0
pve-kernel-6.2: 8.0.5
proxmox-kernel-6.8: 6.8.8-2
proxmox-kernel-6.8.8-2-pve-signed: 6.8.8-2
proxmox-kernel-6.8.4-3-pve-signed: 6.8.4-3
proxmox-kernel-6.5.13-5-pve-signed: 6.5.13-5
proxmox-kernel-6.5: 6.5.13-5
proxmox-kernel-6.5.13-1-pve-signed: 6.5.13-1
proxmox-kernel-6.5.11-8-pve-signed: 6.5.11-8
proxmox-kernel-6.2.16-20-pve: 6.2.16-20
proxmox-kernel-6.2: 6.2.16-20
proxmox-kernel-6.2.16-12-pve: 6.2.16-12
proxmox-kernel-6.2.16-6-pve: 6.2.16-7
pve-kernel-6.2.16-3-pve: 6.2.16-3
ceph-fuse: 17.2.6-pve1+3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx8
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.4
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.7
libpve-cluster-perl: 8.0.7
libpve-common-perl: 8.2.1
libpve-guest-common-perl: 5.1.3
libpve-http-server-perl: 5.1.0
libpve-network-perl: 0.9.8
libpve-rs-perl: 0.8.9
libpve-storage-perl: 8.2.3
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.2.7-1
proxmox-backup-file-restore: 3.2.7-1
proxmox-firewall: 0.4.2
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.2.3
pve-cluster: 8.0.7
pve-container: 5.1.12
pve-docs: 8.2.2
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.1
pve-firewall: 5.0.7
pve-firmware: 3.12-1
pve-ha-manager: 4.0.5
pve-i18n: 3.2.2
pve-qemu-kvm: 9.0.0-5
pve-xtermjs: 5.3.0-3
qemu-server: 8.2.1
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.4-pve1

Found official tutorial in Proxmox wiki but wasn't helpful.
 

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!