Schpammer

Hey! Thanks for your response! Yeah, got access via VNC. Drivers are installed. Is the 8GB RAM limitation only when using the Intel iGPU? I'm thinking about ordering a cheap Nvidia GPU...

Hi! I'm trying to passtrough my iGPU to a Windows VM to use it as Media-PC and throw some output to the TV. I've read through this thread and dozens of others but I'm stuck with error 43... and try to google that... erverything is full of the Nvidia Error 43 😕. My system was not designed to be used as Windows VM to use with my TV but I think there are enough ressources to handle NAS functionallity and the VM. I'm using a J5040-ITX from ASRock with 8 GB RAM. I'm booting Unraid with the following lines but also tried it with stubbing the GPU address and using the Unraid Tool for selecting the iGPU for vfio. kernel /bzimage append pcie_acs_override=downstream,multifunction vfio_iommu_type1.allow_unsafe_interrupts=1 video=efifb:off vesafb:off modprobe.blacklist=i915,snd_hda_intel,snd_hda_codec_hdmi initrd=/bzroot My VM is setup with OVMF and i440fx-5.1 (but also tried it with Seabios and Q35-5.1) and 4GB of RAM. I've tried to boot without GPU BIOS ROM, with the GTV one that was mentioned here and one for the UHD605. When using a vBIOS I'm getting these lines in my dmesg-log (with GTV BIOS) Apr 1 11:29:37 nas kernel: vfio-pci 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Apr 1 11:29:37 nas kernel: br0: port 2(vnet0) entered blocking state Apr 1 11:29:37 nas kernel: br0: port 2(vnet0) entered disabled state Apr 1 11:29:37 nas kernel: device vnet0 entered promiscuous mode Apr 1 11:29:37 nas kernel: br0: port 2(vnet0) entered blocking state Apr 1 11:29:37 nas kernel: br0: port 2(vnet0) entered forwarding state Apr 1 11:29:37 nas kernel: DMAR: DRHD: handling fault status reg 2 Apr 1 11:29:37 nas kernel: DMAR: [DMA Write] Request device [00:02.0] PASID ffffffff fault addr 0 [fault reason 02] Present bit in context entry is clear Apr 1 11:29:38 nas kernel: vfio-pci 0000:00:02.0: vfio_ecap_init: hiding ecap 0x1b@0x100 Apr 1 11:29:38 nas kernel: vfio-pci 0000:00:02.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0x173e Apr 1 11:29:38 nas kernel: vfio-pci 0000:00:02.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0x173e Apr 1 11:29:38 nas kernel: vfio-pci 0000:00:02.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0x173e Apr 1 11:29:38 nas kernel: vfio-pci 0000:00:02.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0x173e I hope there's a chance to get this running and one of you got some good ideas 🙂