Can't get GPU passthrough working again

like this correct?

Code:
GRUB_CMDLINE_LINUX_DEFAULT="quiet pcie_acs_override=downstream,multifunction initcall_blacklist=sysfb_init"
Yes (although you probably don't need the pcie_acs_override). Does cat /proc/cmdline show the same?
To circumvent waiting, this is another log from just now. Seems it's actually forcing a reboot on it's own which is why I can't access it for a little bit.

https://pastebin.com/DFQrxtPq
You are getting timeouts when starting the VM. Are you sure you are not giving it too much memory? Can you test with just 3G instead 16G? Can you attach/share the VM configuration file (/etc/pve/qemu-server/100.conf on the Proxmox host)?
 
well, I'll be damned, that allowed it to start lmao. I'm reinstalling windows on it now. That's so strange. It's on ballooning too. And I had it set to 16 before. But I guess maybe that was when I had 32gb of ram in it. I don't recall. So now, what guide should I go through if I redo it all knowing that was the issue? Should I stick to the beginners guide on the homelab subreddit? That's what I used before. Or does the kernel 5.15 issue still come into play and I need something else?
 
well, I'll be damned, that allowed it to start lmao. I'm reinstalling windows on it now. That's so strange. It's on ballooning too. And I had it set to 16 before. But I guess maybe that was when I had 32gb of ram in it. I don't recall. So now, what guide should I go through if I redo it all knowing that was the issue? Should I stick to the beginners guide on the homelab subreddit? That's what I used before. Or does the kernel 5.15 issue still come into play and I need something else?
Ballooning does not work with passthrough. Because PCIe devices can do DMA at any time to any part of the virtual memory, it must all be pinned into actual host memory.
I don't understand what you are asking. Just set the memory limit to something sensible that works and use initcall_blacklist=sysfb_init when doing passthrough with a NVidia GPU that is also used during boot, on kernel 5.15 or higher.
 
Ballooning does not work with passthrough. Because PCIe devices can do DMA at any time to any part of the virtual memory, it must all be pinned into actual host memory.
I don't understand what you are asking. Just set the memory limit to something sensible that works and use initcall_blacklist=sysfb_init when doing passthrough with a NVidia GPU that is also used during boot, on kernel 5.15 or higher.
Sorry I just meant like, is there anything different from that guide I followed that I should change? And I think the answer is just add the initcall_blacklist=sysfb_init ?
 
Sorry I just meant like, is there anything different from that guide I followed that I should change? And I think the answer is just add the initcall_blacklist=sysfb_init ?
See if you can live without pcie_acs_override=downstream,multifunction, to keep proper secure isolation between VMs and the Proxmox host. I'm willing to have a look at your groups (with the override) and the devices you want to passthrough, to see if we can manage to make it work.
 
So, now I'm stuck again, everything seems to be botting alright, buuut, I'm getting no output on my GPU. When I have primary gpu checked and unchecked. I downloaded the driver and installed it. But it kinda acted weird, said there was a driver update after restarting, and every time I click download, it says download failed. So still all that works right now is console when i have primary gpu unchecked.
 
I don't know how to fix NVidia Windows driver issues (I use neither), but there are several threads on this forum about which version works and which don't.
 
kvm: -device vfio-pci,host=0000:27:00.0,id=hostpci0.0,bus=ich9-pcie-port-1,addr=0x0.0,x-vga=on,multifunction=on: vfio 0000:27:00.0: failed getting region info for VGA region index 8: Invalid argument
device does not support requested feature x-vga
TASK ERROR: start failed: QEMU exited with code 1

After I added

machine: q35
cpu: host,hidden=1,flags=+pcid
args: -cpu 'host,+kvm_pv_unhalt,+kvm_pv_eoi,hv_vendor_id=NV43FIX,kvm=off'
 
I don't know how to fix NVidia Windows driver issues (I use neither), but there are several threads on this forum about which version works and which don't.
okay so figured that out, it starts again, but now i just simply have no display.