windows install stuck in collecting information. nvidia gpu passthrough

spicyisland

New Member
Dec 4, 2019
21
1
3
25
Hi, I'm new to Proxmox and also not good at english but I'll do my best.
I've recently build my desktop pc. My pc parts are like below.
cpu: ryzen 3700x
gpu(host): radeon rx580
gpu(guest): 2070 super
mother board: x570 aorus elite
and memory and so on.
I'd like to passthrough my 2070 super to my windows guest.
I googled many time and tried some settings. I did following settings.

GRUB_CMDLINE_LINUX_DEFAULT="quiet amd_iommu=on iommu=pt"
/etc/modules
vfio
vfio_iommu_type1
vfio_pci
vfio_virqfd
echo "blacklist radeon" >> /etc/modprobe.d/blacklist.conf
echo "blacklist nouveau" >> /etc/modprobe.d/blacklist.conf
echo "blacklist nvidia" >> /etc/modprobe.d/blacklist.conf
echo "options vfio_iommu_type1 allow_unsafe_interrupts=1" > /etc/modprobe.d/iommu_unsafe_interrupts.conf
echo "options vfio-pci ids=<nvidia group> disable_vga=1" > /etc/modprobe.d/vfio.conf
update-grub
update-initramfs -u -k all

/etc/pve/qemu-server/****

args: -cpu host,+kvm_pv_unhalt,+kvm_pv_eoi,hv_vendor_id=NV43FIX,kvm=off
bios: ovmf
bootdisk: scsi0
cores: 4
cpu: host,hidden=1
efidisk0: local-lvm:vm-100-disk-1,size=128K
hostpci0: 09:00,pcie=1,x-vga=1
ide0: local:iso/virtio-win-0.1.171.iso,media=cdrom,size=363020K
ide2: local:iso/Win10_1909_English_x64.iso,media=cdrom
machine: pc-q35-3.1
memory: 16384
name: win10-spicyisland
net0: virtio=C2:DB:35:70:46:59,bridge=vmbr0,firewall=1
numa: 1
ostype: win10
scsi0: local-lvm:vm-100-disk-0,discard=on,iothread=1,size=200G
scsihw: virtio-scsi-single
smbios1: uuid=2a4a668d-3b0f-4743-867a-63cb3d8216d9
sockets: 1
usb0: host=413c:2113,usb3=1
usb1: host=18f8:0fc0,usb3=1
usb2: host=0c76:161e,usb3=1
vga: none
vmgenid: 324aac7e-f016-466c-be3e-04c0edd57f7d

and the windows installation started successfully
but it stuck in collecting information.
Also I can't find any error logs.
I don't know where to look except syslog amd dmesg, they didn't throw any errors.
I also tried to set -machine kernel_irqchip=on and revert pc-q32-3.1 to pc35
It even sometime fails to boot. If it succeeded in booting, it will stuck in collecting information.

I Also followed
https://www.reddit.com/r/homelab/comments/b5xpua/the_ultimate_beginners_guide_to_gpu_passthrough/
this article but if I enabled vga, my virtual machine never boots.(of course I removed x-vga=1)

I connected 2070 super in slot 1 and rx580 in slot 2 and selected slot 2 as primary gpu in bios.
Does this have something to do with this problem?

There is another problem in shutting down virtual machine.
If I try to shutdown dead vm using force off. It will say the machine is turned off but after that I can't shutdown my host computer(I waited for hours) and I can see the virtual machine process running in ps command and I can't kill it even using kill -9 kill -15 kill -30 and so on.
 
Last edited:
Going back a few years i had to use vnc to get the install completed, then pass through the gpu.

I belive when the system collects info it will try to start the graphics card, which may then not graceful reset, causing the box to lock up, just my two cents.
 
Sorry it didn't worked. It will stuck in bios window. I also tried to keep vnc and passed gpu as a pcie device but after that vnc screen stopped working.
 
I completed install without gpu.
After that I tried to change vnc to gpu and failed.
Then I tried to pass gpu not as primary one but it also failed.
 
I take it you've done a clean boot of the host, since the last try ? as the card might need to be reset gracefully.
further than that i'm out of options, having not one this on my box for years now.
 
Yes I did. I'm completely lost now. Even if my settings are exactly the same, there happens different problems.
 
Now I'm stuck in getting files ready for installation. I found that pci passthrough is more stable than pcie passthrough in my setup.
 
I finally get it work by downgrading proxmox to 6.0 !!!
I didn't even need any special settings. I just followed official wiki and added gpu in gui.
However the driver throw error code 43 so I'll fight with it now.
Is this some kind of bug with proxmox 6.1?
 
I finally succeeded to install.
This is my settings in proxmox 6.0

args: -cpu host,+kvm_pv_unhalt,+kvm_pv_eoi,hv_vendor_id=1234567890ab,kvm=off -machine kernel_irqchip=on
bios: ovmf
bootdisk: scsi0
cores: 4
cpu: host,hidden=1
efidisk0: local-lvm:vm-100-disk-1,size=128K
hostpci0: 09:00,pcie=1,x-vga=1
ide2: local:iso/Win10_1909_English_x64.iso,media=cdrom
machine: pc-q35-3.1
memory: 16384
name: win10-spicyisland
net0: virtio=F2:CD:C6:A8:27:A7,bridge=vmbr0,firewall=1
numa: 1
ostype: win10
sata0: local:iso/virtio-win-0.1.171.iso,media=cdrom,size=363020K
sata1: local:iso/nvidia-driver.iso,media=cdrom,size=587348K
scsi0: local-lvm:vm-100-disk-0,iothread=1,size=200G
scsihw: virtio-scsi-single
smbios1: uuid=55d45ec6-e7a9-42ca-88af-10cf1b80ea8d
sockets: 1
usb0: host=413c:2113
usb1: host=18f8:0fc0
vga: none
vmgenid: ???
 
Last edited:
  • Like
Reactions: James Crook
Hi.
Same config, qemu starts, but VM is unusable - it boots almost forever and then fps is near zero, i cannot do anything literally.
 

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!