Search results

Does your ubuntu still works without one of the 2 params (addr / opregion) ? It also means that EFI VM is working with non EFI IGD GPU. at this point I think we have the same setup. Mine is working but I have a 2019 driver version. Each time I'm trying to upgrade I get the code 43. I believe...

I'm not pretty sure about what is doing address=0x18, but I think it is related with PCI bus structure of the VM. Have you tryed a fresh install of windows with my setup ? My VM only runs with old IFGX drivers (the one from the windows fresh install)

Can you try a fresh install of the VM now ? Or start to uninstall the driver ? Mine is older than that (2019 if I remeber ?). Each time I'm trying a driver update I lose go back to error 43...

note that I forgot something really important in m previous message : addr=0x18 in the arg section. It surely can be that ! :)

Here are the diff : GRUB_CMDLINE_LINUX_DEFAULT="consoleblank=0 intel_iommu=on vfio-pci.ids=8086:3ea5 video=efifb:off video=vesafb:off" GRUB_CMDLINE_LINUX="" agent: 1 args: -device vfio-pci,host=00:02.0,addr=0x18,x-igd-opregion=on bootdisk: scsi0 cores: 6 cpu: host machine: q35 memory: 8192...

Hi @miqu, I don't have access to my proxmox rigth now, but you have to try: -device vfio-pci,host=00:02.0,x-igd-opregion=on bios: seabios instead of hostpci0: 00:02,pcie=1,x-vga=1 bios: ovmf I also disable Legacy booting mode in the BIOS but I'm not really sure if it's relevant Let me...

Hi, I managed to make it working on NUC8I7BEH. In my opinion, on NUC, Intel IGD is not EFI. I managed to make it working with SeaBIOS but did not really tried OVMF Everything is working fine as long as I don't upgrade the default windows driver. Anytime I'm trying to upgrade IGD driver (with...

You should try to enable MSI in your windows guest. Check other post in the forum about this

Take care, in your lspci for your GPU I can see Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+ That could lead to a code 43. check in other posts how to enable MSI in windows guest VM

yes

you can try to sniff network traffic using tcpdump but if there is lot of network load it will be hard to find the relevant packets

I don't run Linux VM with GPU passthru, only win10 I don't have my config here but I followed the guide https://pve.proxmox.com/wiki/Pci_passthrough just used this to add GPU to the VM : args: -device vfio-pci,host=00:02.0,addr=0x18,x-vga=on,x-igd-opregion=on

Hello, Your GPU has loaded radeon driver so I think you cannot bind vfio on it. in the guide, have you followed this section ? echo "options vfio-pci ids=10de:1381,10de:0fbc" > /etc/modprobe.d/vfio.conf and blacklisted radeon driver ? echo "blacklist radeon" >> /etc/modprobe.d/blacklist.conf...

Hello, I don't see Error 43 anymore since last update (5.4.44-2-pve), but still some random crash (soft lockup). Not sure it's related to GPU passthrough. Have you tried booting your VM with nomodeset and/or i915.modeset=0 grub option ?

Hello, same issue here on NUC8I7BEH. I tried the workaroud and it's not working even with the full offload disabled : ethtool -K eno1 gso off gro off tso off tx off rx off rxvlan off txvlan off sg off I don't have intensive network use but when I spawn a win 10 VM (with GPU throughput) the...

Hi Flatline, I've got a NUB8I7BEH and manage to have it working… Until Proxmox 6.2. I'm still looking for a stable solution. You should not use : hostpci0: 00:02,pcie=1,rombar=0,x-vga=1 But instead : args: -device vfio-pci,host=00:02.0,addr=0x18,x-vga=on,x-igd-opregion=on Anyway, this...