simt

Hi WizP, keep on trying, I've been trying some more too. Hopefully one of will get there. In short, I tried adding a binding in my Unraid go file. But what made more difference was I've changed my Ubuntu VM to use an i440 instead of Q35. I've stopped getting the memory conflict errors - which is great. However I'm getting an error regarding the vbios rom I'm passing through in the VM setup. Dmesg in the Ubuntu VM complains that it was expecting a 05xa header, but got something else. Which is really strange because that vbios I have here does start with 05xa. I'm going to try passing it in through a QEMU argument instead. Failing that might run the vbios through 'rom-parser' and see if it changes anything. -Simt

I'd appreciate it, if you could have a look. intel_uhd_605_vbios.zip I've attached the vbios file I have. I downloaded it from another forum, Proxmox maybe..? I've been trying to figure out where I got it from last week. But can't. If I remember I'll edit this post. Edit: Got the vbios from: https://forum.proxmox.com/threads/proxmox-6-0-gemini-lake-and-igd-graphics-passthrough-for-windows-10.60415/post-287483 -Simt

okay, I've been working through the solution from here: https://forum.proxmox.com/threads/proxmox-5-2-gemini-lake-and-igd-graphics-passthrough-for-ubuntu-18.47129/page-2 I'm good right until the very end. At that point in Proxmox, Steffen makes a new VM, with regular settings, but then he does this: Video: add PCI Device 0000 00:02.0 -> select advanced + select PCI-Express + Primary GPU + All Functions +ROM-Bar Sound (HDMI) add PCI Device 0000 00:0e.0 -> select advanced + select PCI-Express + All Functions +ROM-Bar And the resulting lines in the config file (I guess is Proxmox XML equivalent: hostpci0: 00:02,pcie=1,x-vga=1 hostpci1: 00:0e,pcie=1 I'm not sure how to do this in Unraid. Could anyone help please? And up to here with everything else, passthorugh isn't working. I tried adding a QEMU section at the end of the XML: <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=00:02.0,bus=pcie.0,x-vga=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=00:0e.0,bus=pcie.0'/> </qemu:commandline> But this gives me an execution error on starting the VM: internal error: qemu unexpectedly closed the monitor: 2020-03-23T12:58:48.602152Z qemu-system-x86_64: -device vfio-pci,host=0000:00:02.0,id=hostdev0,bus=pcie.0,addr=0x2: IGD device 0000:00:02.0 cannot support legacy mode due to existing devices at address 1f.0 2020-03-23T12:58:48.760743Z qemu-system-x86_64: -device vfio-pci,host=00:02.0,bus=pcie.0,x-vga=on: vfio 0000:00:02.0: device is already attached By the way, when I look at what's at 1f.0 in Unraid (Unraid terminal> lspci -knn) I see: 00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:31e8] (rev 03) Lastly, I'll add that everything that Steffenprox did, tranlsated to a bunch of arguments that went into the Unraid sysconfig file. Mine looks like this: kernel /bzimage append intel_iommu=on vfio_virqfd vfio_pci vfio-pci.ids=8086:3185,8086:3198 modprobe.blacklist=snd_hda_intel,snd_hda_codec_hdmi,i915 pcie_acs_override=downstream,multifunction video=efifb:off,vesafb:off vfio_iommu_type1.allow_unsafe_interrupts=1 initrd=/bzroot

Hi Wizp, I saw that post early on in my efforts to get passthrough working. Back then it seemed way too arcane and complicated to try. But looking at it again now, it's like a nonchalant 'oh yeah, doesn't look to hard to follow, I could give that a good try.' I'm out camping at the moment (possibly last time for awhile as I just heard that some state borders are being shut here in Australia due to Coronavirus) But when we're back, I'll give it a try. -Simt

Hello, I'm hoping someone can help me figure this out and get passthrough working. I have an Asrock J4105 with an Intel Quad-core processor and onboard Intel UHD605 graphics. I've installed Unraid (loving it), but it's also a real desire of mine to use the machine as a media player. I've been trying to passthrough the UHD605 to a VM of Ubuntu. (Though I'll take any OS, if passthrough to it can work.). After much scouring of forums, I've gotten to a point where Ubuntu VM runs happily from the DVI output. But the video card is still never recognised properly and I can't get hardware acceleration to effectively play video files. A bare metal host install of Ubuntu works absolutely fine with the UHD605 card. In 'good' host Ubuntu settings I see this, and it's what I want: But in VM Ubuntu what I get instead is: My Unraid OS syslinux config is: Unraid OS: kernel /bzimage append pcie_acs_override=downstream,multifunction vfio-pci.ids=8086:0412,8086:a170 video=efifb:off,vesafb:off vfio_iommu_type1.allow_unsafe_interrupts=1 initrd=/bzroot I was using a modprobe.blacklist=.... But it didn't seem to make any difference. I'm even supplying a Video Rom bios of the UHD605 - which doesn't seem to make much difference either way. My VMS settings has PCIe override set to: Both, and VFIO Allow unsafe interrupts is: Yes. But still with all that, I can't get proper passthrough. When I look through Dmesg in Ubuntu I see the following error that I think is the culprit: [drm:i915_gem_init_stolen [i915]] *ERROR* conflict detected with stolen region: [mem 0x70000000-0x7fffffff] My Ubuntu VM log from Unraid looks like this: ErrorWarningSystemArrayLogin -overcommit mem-lock=off \ -smp 2,sockets=1,cores=2,threads=1 \ -uuid a2e91254-bd7c-8e33-fcf6-cc9a5f85ce29 \ -display none \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=33,server,nowait \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=utc,driftfix=slew \ -global kvm-pit.lost_tick_policy=delay \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device pcie-root-port,port=0xb,chassis=4,id=pci.4,bus=pcie.0,addr=0x1.0x3 \ -device pcie-root-port,port=0x8,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x1 \ -device pcie-root-port,port=0x9,chassis=2,id=pci.2,bus=pcie.0,addr=0x1.0x1 \ -device pcie-root-port,port=0xa,chassis=3,id=pci.3,bus=pcie.0,addr=0x1.0x2 \ -device ich9-usb-ehci1,id=usb,bus=pcie.0,addr=0x7.0x7 \ -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pcie.0,multifunction=on,addr=0x7 \ -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pcie.0,addr=0x7.0x1 \ -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pcie.0,addr=0x7.0x2 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.2,addr=0x0 \ -blockdev '{"driver":"file","filename":"/mnt/user/domains/Ubuntu-19_2nd/vdisk1.img","node-name":"libvirt-1-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-1-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-1-storage"}' \ -device ide-hd,bus=ide.2,drive=libvirt-1-format,id=sata0-0-2,bootindex=1,write-cache=on \ -netdev tap,fd=35,id=hostnet0,vhost=on,vhostfd=36 \ -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:2b:b5:3f,bus=pci.1,addr=0x0 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0 \ -chardev socket,id=charchannel0,fd=38,server,nowait \ -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -device vfio-pci,host=0000:00:02.0,id=hostdev0,bus=pcie.0,addr=0x2,romfile=/mnt/user/isos/VBIOS/intel_uhd_605_vbios/intel_uhd_605_vbios.rom \ -device vfio-pci,host=0000:00:0e.0,id=hostdev1,bus=pci.3,addr=0x0 \ -device usb-host,hostbus=1,hostaddr=2,id=hostdev2,bus=usb.0,port=1 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2020-03-18 12:43:33.085+0000: Domain id=3 is tainted: high-privileges 2020-03-18 12:43:33.085+0000: Domain id=3 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2020-03-18T12:43:34.592367Z qemu-system-x86_64: -device vfio-pci,host=0000:00:02.0,id=hostdev0,bus=pcie.0,addr=0x2,romfile=/mnt/disk1/isos/VBIOS/intel_uhd_605_vbios/intel_uhd_605_vbios.rom: IGD device 0000:00:02.0 cannot support legacy mode due to existing devices at address 1f.0 And the Dmesg grepped for only i915 stuff looks like this: You'll see there's errors about failing to initialise GPU and declaring it wedged! sim@sim-Standard-PC-Q35-ICH9-2009:~$ dmesg | grep -iC 3 "i915" [ 7.401484] intel_telemetry_core Init [ 7.413539] Invalid pltconfig, ensure IPC1 device is enabled in BIOS [ 7.443107] Invalid pltconfig, ensure IPC1 device is enabled in BIOS [ 7.516713] i915 0000:00:02.0: vgaarb: deactivate vga console [ 7.516844] [drm:i915_gem_init_stolen [i915]] *ERROR* conflict detected with stolen region: [mem 0x70000000-0x7fffffff] [ 7.521727] [drm] couldn't get memory information [ 7.572927] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 7.572929] [drm] Driver supports precise vblank timestamp query. [ 7.572972] i915 0000:00:02.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0x0000 [ 7.572976] [drm] Failed to find VBIOS tables (VBT) [ 7.587479] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 7.598615] [drm] Applying Increase DDI Disabled quirk [ 7.641456] [drm] Finished loading DMC firmware i915/glk_dmc_ver1_04.bin (v1.4) [ 8.288163] audit: type=1400 audit(1584535434.498:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=485 comm="apparmor_parser" [ 8.289205] audit: type=1400 audit(1584535434.498:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=485 comm="apparmor_parser" [ 8.290194] audit: type=1400 audit(1584535434.498:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=485 comm="apparmor_parser" -- [ 8.403693] [drm] RC6 disabled by BIOS [ 8.403694] [drm] RC6 disabled, disabling runtime PM support [ 8.501351] audit: type=1400 audit(1584535434.710:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/cups-browsed" pid=489 comm="apparmor_parser" [ 8.626603] i915 0000:00:02.0: Failed to idle engines, declaring wedged! [ 8.664155] audit: type=1400 audit(1584535434.874:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=490 comm="apparmor_parser" [ 8.698558] i915 0000:00:02.0: Failed to initialize GPU, declaring it wedged! [ 8.698565] i915 0000:00:02.0: Please file a bug at https://bugs.freedesktop.org/enter_bug.cgi?product=DRI against DRM/Intel providing the dmesg log by booting with drm.debug=0xf [ 8.719360] [drm] Initialized i915 1.6.0 20190619 for 0000:00:02.0 on minor 0 [ 8.719589] snd_hda_intel 0000:03:00.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 9.014624] fbcon: i915drmfb (fb0) is primary device [ 9.014694] Console: switching to colour frame buffer device 240x75 [ 9.014736] i915 0000:00:02.0: fb0: i915drmfb frame buffer device [ 9.252442] audit: type=1400 audit(1584535435.462:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=491 comm="apparmor_parser" [ 9.257476] audit: type=1400 audit(1584535435.466:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=491 comm="apparmor_parser" [ 9.260483] audit: type=1400 audit(1584535435.470:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=491 comm="apparmor_parser" The LSPCI look like this: 00:00.0 Host bridge: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller 00:01.0 PCI bridge: Red Hat, Inc. QEMU PCIe Root port 00:01.1 PCI bridge: Red Hat, Inc. QEMU PCIe Root port 00:01.2 PCI bridge: Red Hat, Inc. QEMU PCIe Root port 00:01.3 PCI bridge: Red Hat, Inc. QEMU PCIe Root port 00:02.0 VGA compatible controller: Intel Corporation Device 3185 (rev 03) 00:07.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:07.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:07.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:07.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1f.0 ISA bridge: Intel Corporation 82801IB (ICH9) LPC Interface Controller (rev 02) 00:1f.2 SATA controller: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] (rev 02) 00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 02) 01:00.0 Ethernet controller: Red Hat, Inc. Virtio network device (rev 01) 02:00.0 Communication controller: Red Hat, Inc. Virtio console (rev 01) 03:00.0 Audio device: Intel Corporation Device 3198 (rev 03) If anyone has any ideas, I would greatly appreciate it. -Simt

Hi uldise, That worked like a charm. Pointed to 'sda' rather than 'sda1', and now Unraid happily recognises and mounts the disk. Thankyou. I do feel what your saying. I really would have preferred to have Unraid as the host 'bare metal' OS and a VM of whatever running to play media. But I spent 'a lot' of hours trying to passthrough the onboard UHD605 graphics to get non-choppy playback. I might go ask for some help in a relevant Unraid thread on that issue. For now, I'll try out Unraid as a guest in Virtualbox, see what issues pop up (I already don't like that I can't get SMART data for the disks) and if performance is sufficient or not. If it is all okay, great! Otherwise I'll bite the bullet and buy a little raspberry Pi4 or similar to be the media player. I just so wanted to do it all in a single low-power box. (Currently with 2 hdd + 1 sdd, when I'm playing a mkv - TPD: 23W. Idle: ~10W) simt

Hi all, I'm running Unraid as a vm in VirtualBox on top of an Ubuntu host. Unraid however is not liking the raw 10TB disk being passed to it by Virtualbox. Both Virtualbox and Unraid are giving me warnings about the disk. I'm asking in the Virtualbox forums, but also thought I'd ask here in case someone might know a workaround. Vbox warning warning message is: The medium '/home/home/VirtualBox VMs/unraid_home/First_10TB.vmdk' has a logical size of 9TB but the file system the medium is located on can only handle files up to 7TB in theory. We strongly recommend to put all your virtual disk images and the snapshot folder onto a proper file system (e.g. ext3) with a sufficient size. Error ID: FatPartitionDetected Severity: Warning This is a 10TB disk that had already been formatted by a bare metal host Unraid earlier with a single XFS partition. I'm pointing to the raw disk with a VMDK file that's given to Vbox. The disk status in Unraid is: VBOX_HARDDISK_VBf91b0b21-d343ebca - 10 TB (sdc) Name: Disk 1 Partition size: 9,766,436,764 KB (K=1024) Partition format: unknown File system status: Unmountable: Unsupported partition layout File system type: auto (greyed out) Any ideas on how I could fix this from Unraid's end? For anyone who's curious I've attached the VMDK file as a text file. Let me know if there's any other logs that might be useful for diagnosing. p.s. Why Unraid as a VM? -Because I'd like to use my little machine (Asrock J4105) as both a Unraid server and a media player. However after much trying I couldn't get Unraid to successfully pass through the integrated Intel UHD600 video to whatever VM I ran in Unraid. So now I'm trying the other way around. 'regards, Simt First_10TB.vmdk