Proxmox PCI-E Passthrough to host monitor?

Vendor-reset is working and it looks like you added the USB controller. Do you have output on the display? Any errors or logs from Windows?
I see a "_" blinking on the screen the whole time when i start the VM now, but thats it... oh this isn't the usb controller, just Motherboard I/O
 
I see a "_" blinking on the screen the whole time when i start the VM now, but thats it... oh this isn't the usb controller, just Motherboard I/O
As least it is not disabling the screen and/or the screen does not turn off because it is not receiving a signal. You're right: reset full-speed USB device number ... is probably one of your four usb passthroughs, not a USB controller as a whole. I have more experience with GPU passthrough to a Ubuntu VM than Windows. Maybe someone else know what a blinking cursor means inside a VM booting Windows?
 
As least it is not disabling the screen and/or the screen does not turn off because it is not receiving a signal. You're right: reset full-speed USB device number ... is probably one of your four usb passthroughs, not a USB controller as a whole. I have more experience with GPU passthrough to a Ubuntu VM than Windows. Maybe someone else know what a blinking cursor means inside a VM booting Windows?
Also Proxmox keeps crashing, dammit that happends sometimes too it become unresponsive and its gone

Yeah it wouldnt help there is a massive shortage on GPUs soo installing a cheap one just for nonesense avoidance is not an option rn

or maybe it is, just no guarantees it'll work

Proxmox crash upon VM boot
 
Last edited:
My VM configuration with RX570 passthrough is very similar to yours, except for all the args=, hidden=1, pcie=1, x-vga=1 and noi vcpus= and runs Ubuntu20.04 LTS fine. Could you try a Linux LiveCD instead of starting Windows? This might give more information.
Is there anything useful in the Syslog or journalctl from just before the crash? Does it always crash at the first attempt to start the VM?
 
My VM configuration with RX570 passthrough is very similar to yours, except for all the args=, hidden=1, pcie=1, x-vga=1 and noi vcpus= and runs Ubuntu20.04 LTS fine. Could you try a Linux LiveCD instead of starting Windows? This might give more information.
Is there anything useful in the Syslog or journalctl from just before the crash? Does it always crash at the first attempt to start the VM?
It crashed after Windows 10 installed AMD drivers

also i dont use those arguments anymore like you told me
 
Last edited:
I don't know how to troubleshoot Windows or AMD's Windows drivers, sorry. Maybe someone else knows how to approach this?
I only know how to troubleshoot Linux and on the virtual hardware-level they are the same. That's why I suggest booting from a Ubuntu 20.04 LiveCD to see if that will work.
bios: ovmf boot: order=scsi1;scsi0 cores: 3 cpu: host,flags=+virt-ssbd efidisk0: qpool-zfs:vm-126-disk-0,size=1M hostpci0: 0c:00 hotplug: 0 memory: 3072 name: media26 net0: virtio=52:54:56:00:01:26,bridge=vmbr0,firewall=1 numa: 0 onboot: 1 ostype: l26 rng0: source=/dev/urandom scsi0: qpool-zfs:vm-126-disk-1,cache=writeback,discard=on,size=32G,ssd=1 scsi1: none,media=cdrom scsihw: virtio-scsi-pci serial0: socket sockets: 1 tablet: 0 vga: serial0