paperblankets

My unraid setup has a mix of hds, nvme drives, and sata ssds. My ideal temps for running nvme drives is pretty high compared to other drives, 45-50c. Are there plans to allow per drive temp thresholds? Or is this a feature that exists but I have failed to find via search? Thanks for your time,

I am not sure if I needed to restart the server, or have the array stopped, but one of those let me run two of the 3 commands: echo 0 > /sys/class/vtconsole/vtcon0/bind echo efi-framebuffer.0 > /sys/bus/platform/drivers/efi-framebuffer/unbind Which resulted in a boot without mmap errors, which allowed me to install drivers. @bigjme I added a user script to fix mmap, it sounds like this fix does not persist on a restart for you right? Thank you for the debugging steps and suggestions!

Thanks for the info Jamie! I indeed get a different result when ssh'ed as root. I am still running into issues though. Last login: Thu Aug 9 19:06:02 2018 from 192.168.1.125 Linux 4.14.49-unRAID. root@HuananTheHydra:~# echo 0 > /sys/class/vtconsole/vtcon0/bind -bash: /sys/class/vtconsole/vtcon0/bind: No such file or directory root@HuananTheHydra:~# echo 0 > /sys/class/vtconsole/vtcon1/bind -bash: /sys/class/vtconsole/vtcon1/bind: No such file or directory root@HuananTheHydra:~# echo efi-framebuffer.0 > /sys/bus/platform/drivers/efi-framebuffer/unbind -bash: /sys/bus/platform/drivers/efi-framebuffer/unbind: No such file or directory My vtcon* directories do not contain a bind folder. root@HuananTheHydra:~# /sys/class/vtconsole/vtcon0/ power/ subsystem/ root@HuananTheHydra:~# /sys/class/vtconsole/vtcon1/ power/ subsystem/

I get similar mmap errors to what you describe, and have the same issues on driver install. When I run the following in the webterminal: echo 0 > /sys/class/vtconsole/vtcon1/bind I get -bash: echo: command not found When I run: sudo echo efi-framebuffer.0 > /sys/bus/platform/drivers/efi-framebuffer/unbind  I get: /sys/bus/platform/drivers/efi-framebuffer/unbind: Permission denied Any thoughts? I made a post here: but have not gotten any feedback thus far.

Hello, I am attempting to install Nvidia GPU Drivers in a windows 10 vm. Unraid version: 6.5.3 Nvidia Driver version: 398.36 Install types attempted: Clean, just graphics, graphics and audio, all parts OS: Windows 10 17134 IOMMU Groups (All video card stuff is in 21): IOMMU group 0: [8086:0e00] 00:00.0 Host bridge: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 DMI2 (rev 04) IOMMU group 1: [8086:0e02] 00:01.0 PCI bridge: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI Express Root Port 1a (rev 04) IOMMU group 2: [8086:0e04] 00:02.0 PCI bridge: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI Express Root Port 2a (rev 04) IOMMU group 3: [8086:0e08] 00:03.0 PCI bridge: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI Express Root Port 3a (rev 04) IOMMU group 4: [8086:0e20] 00:04.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 0 (rev 04) [8086:0e21] 00:04.1 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 1 (rev 04) [8086:0e22] 00:04.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 2 (rev 04) [8086:0e23] 00:04.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 3 (rev 04) [8086:0e24] 00:04.4 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 4 (rev 04) [8086:0e25] 00:04.5 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 5 (rev 04) [8086:0e26] 00:04.6 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 6 (rev 04) [8086:0e27] 00:04.7 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 7 (rev 04) IOMMU group 5: [8086:0e28] 00:05.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 VTd/Memory Map/Misc (rev 04) [8086:0e2a] 00:05.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 IIO RAS (rev 04) [8086:0e2c] 00:05.4 PIC: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 IOAPIC (rev 04) IOMMU group 6: [8086:1d3e] 00:11.0 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Virtual Root Port (rev 06) IOMMU group 7: [8086:1d3a] 00:16.0 Communication controller: Intel Corporation C600/X79 series chipset MEI Controller #1 (rev 05) IOMMU group 8: [8086:1d2d] 00:1a.0 USB controller: Intel Corporation C600/X79 series chipset USB2 Enhanced Host Controller #2 (rev 06) IOMMU group 9: [8086:1d20] 00:1b.0 Audio device: Intel Corporation C600/X79 series chipset High Definition Audio Controller (rev 06) IOMMU group 10: [8086:1d10] 00:1c.0 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Root Port 1 (rev b6) IOMMU group 11: [8086:1d12] 00:1c.1 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Root Port 2 (rev b6) IOMMU group 12: [8086:1d14] 00:1c.2 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Root Port 3 (rev b6) IOMMU group 13: [8086:1d16] 00:1c.3 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Root Port 4 (rev b6) IOMMU group 14: [8086:1d18] 00:1c.4 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Root Port 5 (rev b6) IOMMU group 15: [8086:1d1a] 00:1c.5 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Root Port 6 (rev b6) IOMMU group 16: [8086:1d1c] 00:1c.6 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Root Port 7 (rev b6) IOMMU group 17: [8086:1d1e] 00:1c.7 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Root Port 8 (rev b6) IOMMU group 18: [8086:1d26] 00:1d.0 USB controller: Intel Corporation C600/X79 series chipset USB2 Enhanced Host Controller #1 (rev 06) IOMMU group 19: [8086:244e] 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a6) IOMMU group 20: [8086:1d41] 00:1f.0 ISA bridge: Intel Corporation C600/X79 series chipset LPC Controller (rev 06) [8086:1d02] 00:1f.2 SATA controller: Intel Corporation C600/X79 series chipset 6-Port SATA AHCI Controller (rev 06) [8086:1d22] 00:1f.3 SMBus: Intel Corporation C600/X79 series chipset SMBus Host Controller (rev 06) IOMMU group 21: [10de:1b81] 02:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1070] (rev a1) [10de:10f0] 02:00.1 Audio device: NVIDIA Corporation GP104 High Definition Audio Controller (rev a1) IOMMU group 22: [1b4b:9215] 05:00.0 SATA controller: Marvell Technology Group Ltd. Device 9215 (rev 11) IOMMU group 23: [10ec:8168] 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) IOMMU group 24: [1106:3483] 07:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01) IOMMU group 25: [1106:3483] 08:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01) IOMMU group 26: [8086:0e80] ff:08.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 QPI Link 0 (rev 04) IOMMU group 27: [8086:0e90] ff:09.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 QPI Link 1 (rev 04) IOMMU group 28: [8086:0ec0] ff:0a.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Power Control Unit 0 (rev 04) [8086:0ec1] ff:0a.1 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Power Control Unit 1 (rev 04) [8086:0ec2] ff:0a.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Power Control Unit 2 (rev 04) [8086:0ec3] ff:0a.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Power Control Unit 3 (rev 04) IOMMU group 29: [8086:0e1e] ff:0b.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 UBOX Registers (rev 04) [8086:0e1f] ff:0b.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 UBOX Registers (rev 04) IOMMU group 30: [8086:0ee0] ff:0c.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04) [8086:0ee2] ff:0c.1 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04) [8086:0ee4] ff:0c.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04) [8086:0ee6] ff:0c.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04) [8086:0ee8] ff:0c.4 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04) IOMMU group 31: [8086:0ee1] ff:0d.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04) [8086:0ee3] ff:0d.1 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04) [8086:0ee5] ff:0d.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04) [8086:0ee7] ff:0d.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04) [8086:0ee9] ff:0d.4 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04) IOMMU group 32: [8086:0ea0] ff:0e.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Home Agent 0 (rev 04) [8086:0e30] ff:0e.1 Performance counters: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Home Agent 0 (rev 04) IOMMU group 33: [8086:0ea8] ff:0f.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Target Address/Thermal Registers (rev 04) [8086:0e71] ff:0f.1 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 RAS Registers (rev 04) [8086:0eaa] ff:0f.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder Registers (rev 04) [8086:0eab] ff:0f.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder Registers (rev 04) [8086:0eac] ff:0f.4 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder Registers (rev 04) [8086:0ead] ff:0f.5 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder Registers (rev 04) IOMMU group 34: [8086:0eb0] ff:10.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 Thermal Control 0 (rev 04) [8086:0eb1] ff:10.1 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 Thermal Control 1 (rev 04) [8086:0eb2] ff:10.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 ERROR Registers 0 (rev 04) [8086:0eb3] ff:10.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 ERROR Registers 1 (rev 04) [8086:0eb4] ff:10.4 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 Thermal Control 2 (rev 04) [8086:0eb5] ff:10.5 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 Thermal Control 3 (rev 04) [8086:0eb6] ff:10.6 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 ERROR Registers 2 (rev 04) [8086:0eb7] ff:10.7 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 ERROR Registers 3 (rev 04) IOMMU group 35: [8086:0e1d] ff:13.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 R2PCIe (rev 04) [8086:0e34] ff:13.1 Performance counters: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 R2PCIe (rev 04) [8086:0e81] ff:13.4 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 QPI Ring Registers (rev 04) [8086:0e36] ff:13.5 Performance counters: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 QPI Ring Performance Ring Monitoring (rev 04) IOMMU group 36: [8086:0ec8] ff:16.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 System Address Decoder (rev 04) [8086:0ec9] ff:16.1 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Broadcast Registers (rev 04) [8086:0eca] ff:16.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Broadcast Registers (rev 04) Logs once install hangs: 2018-07-20T02:48:59.104014Z qemu-system-x86_64: -device vfio-pci,host=02:00.0,id=hostdev0,bus=pci.0,addr=0x5,romfile=/mnt/disk7/gpudumps/GeForce GTX 1070 Mini ITX OC 8G/modified bios/193322.rom: Failed to mmap 0000:02:00.0 BAR 3. Performance may be slow 2018-07-20T03:01:20.305808Z qemu-system-x86_64: vfio_region_write(0000:02:00.0:region3+0x40a8, 0x1fffe101,8) failed: Device or resource busy KVM internal error. Suberror: 1 emulation failure RAX=ffffbb7ed7615000 RBX=ffffbb7ed7615000 RCX=ffffbb7ed7615000 RDX=0000000000000000 RSI=ffffd7039fba6830 RDI=ffffd7039ffc2000 RBP=ffffd7039f6ba000 RSP=ffffa904275f60c8 R8 =0000000000001000 R9 =0101010101010101 R10=fffff803eb23e46c R11=ffffa904275f5e80 R12=ffffd703a10eeab0 R13=ffffd7039f8d7010 R14=0000000000000000 R15=0000000000100000 RIP=fffff803eb590338 RFL=00010216 [----AP-] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES =002b 0000000000000000 ffffffff 00c0f300 DPL=3 DS [-WA] CS =0010 0000000000000000 00000000 00209b00 DPL=0 CS64 [-RA] SS =0018 0000000000000000 00000000 00409300 DPL=0 DS [-WA] DS =002b 0000000000000000 ffffffff 00c0f300 DPL=3 DS [-WA] FS =0053 0000000000000000 0000fc00 0040f300 DPL=3 DS [-WA] GS =002b ffffab808dd79000 ffffffff 00c0f300 DPL=3 DS [-WA] LDT=0000 0000000000000000 ffffffff 00c00000 TR =0040 ffffab808dd8b000 00000067 00008b00 DPL=0 TSS64-busy GDT= ffffab808dd8cfb0 00000057 IDT= ffffab808dd8a000 00000fff CR0=80050033 CR2=ffffbf80bd7f4000 CR3=00000000001ad000 CR4=001506f8 DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 DR6=00000000ffff0ff0 DR7=0000000000000400 EFER=0000000000000d01 Code=66 66 66 66 0f 1f 84 00 00 00 00 00 66 48 0f 6e c2 0f 16 c0 <0f> 11 01 4c 03 c1 48 83 c1 10 48 83 e1 f0 4c 2b c1 4d 8b c8 49 c1 e9 07 74 2f 0f 29 01 0f I have dumped the bios for the card myself, and it seems to be detected properly. VM xml: <domain type='kvm' id='7'> <name>Windows 10 GPU powered</name> <uuid>9bbfa0b2-3543-fda4-0e7e-1872da3c997c</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>10</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='11'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='12'/> <vcpupin vcpu='4' cpuset='3'/> <vcpupin vcpu='5' cpuset='13'/> <vcpupin vcpu='6' cpuset='4'/> <vcpupin vcpu='7' cpuset='14'/> <vcpupin vcpu='8' cpuset='5'/> <vcpupin vcpu='9' cpuset='15'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.11'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/9bbfa0b2-3543-fda4-0e7e-1872da3c997c_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='5' threads='2'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Windows 10 GPU powered/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.141-1.iso'/> <backingStore/> <target dev='hdb' bus='ide'/> <readonly/> <alias name='ide0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='ide' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:a3:75:38'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/1'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/1'> <source path='/dev/pts/1'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-7-Windows 10 GPU power/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'> <alias name='input0'/> </input> <input type='keyboard' bus='ps2'> <alias name='input1'/> </input> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/user/gpudumps/GeForce GTX 1070 Mini ITX OC 8G/modified bios/193322.rom'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0c45'/> <product id='0x5101'/> <address bus='3' device='3'/> </source> <alias name='hostdev2'/> <address type='usb' bus='0' port='1'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </memballoon> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain> PCIe ACS Override is enabled I get the following message when I start my vm: 2018-07-20T03:05:44.601614Z qemu-system-x86_64: -device vfio-pci,host=02:00.0,id=hostdev0,bus=pci.0,addr=0x5,romfile=/mnt/disk7/gpudumps/GeForce GTX 1070 Mini ITX OC 8G/modified bios/193322.rom: Failed to mmap 0000:02:00.0 BAR 3. Performance may be slow What should my next debugging steps be? What other information is helpful debugging something like this? Thanks for your time

Hello, I am setting up gpu pass-through for the first time and think I need some help. The problem: When booting my vm with a bios dump (acquired following these methods from Spaceinvader One: bios modification, general dump usage) 2018-06-24 15:08:41.455+0000: starting up libvirt version: 4.0.0, qemu version: 2.11.1, hostname: HuananTheHydra LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'guest=Windows 10,debug-threads=on' -S -object 'secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-11-Windows 10/master-key.aes' -machine pc-i440fx-2.11,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=none -drive file=/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/etc/libvirt/qemu/nvram/9bbfa0b2-3543-fda4-0e7e-1872da3c997c_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 8192 -realtime mlock=off -smp 10,sockets=1,cores=5,threads=2 -uuid 9bbfa0b2-3543-fda4-0e7e-1872da3c997c -display none -no-user-config -nodefaults -chardev 'socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-11-Windows 10/monitor.sock,server,nowait' -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device TX 1070 Mini ITX OC 8G/modified bios/Gigabyte.GTX1070.mini.rom' -device vfio-pci,host=02:00.1,id=hostdev1,bus=pci.0,addr=0x6 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=on 2018-06-24 15:08:41.455+0000: Domain id=11 is tainted: high-privileges 2018-06-24 15:08:41.455+0000: Domain id=11 is tainted: host-cpu 2018-06-24T15:08:41.526591Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0) 2018-06-24T15:08:42.672504Z qemu-system-x86_64: -device vfio-pci,host=02:00.0,id=hostdev0,bus=pci.0,addr=0x5,romfile=/mnt/disk7/gpudumps/GeForce GTX 1070 Mini ITX OC 8G/modified bios/Gigabyte.GTX1070.mini.rom: Failed to mmap 0000:02:00.0 BAR 3. Performance may be slow I came to the conclusion the vm does not boot because: The attached videocard (GeForce GTX 1070 Mini ITX OC 8G) does not output anything The MAC address of the VM never appears on my network. What I have tried: The same vm configuration, with a vnc graphic card (QXL) The same vm configuration, without the bios, with a vnc graphic card (QXL) The same vm configuration, without the bios The same vm configuration, without the bios The attached videocard (GeForce GTX 1070 Mini ITX OC 8G) does not output anything The MAC address of the VM never appears on my network. Code 43 appears The same vm configuration, without the bios, with a vnc graphic card (QXL) The attached videocard (GeForce GTX 1070 Mini ITX OC 8G) does not output anything The MAC address of the VM never appears on my network. Code 43 appears The same vm configuration, with a vnc graphic card (QXL) The MAC address of the VM does appear on my network/I can not remote in The attached videocard (GeForce GTX 1070 Mini ITX OC 8G) does not output anything System information: GPU I am attempting to pass-through: GeForce GTX 1070 Mini ITX OC 8G Unraid 6.5.3 Model: Custom M/B: HUANANZHI - X79 CPU: Intel® Xeon® CPU E5-2670 v2 @ 2.50GHz HVM: Enabled IOMMU: Enabled Cache: 640 kB, 2560 kB, 25600 kB Memory: 32 GB (max. installable capacity 96 GB) Network: bond0: fault-tolerance (active-backup), mtu 1500 eth0: 1000 Mb/s, full duplex, mtu 1500 Kernel: Linux 4.14.49-unRAID x86_64 OpenSSL: 1.0.2o Full details are attached in unraidHardwareDetails.xml Other information: Windows build is 16299 I am attempting to install my nvidia driver via Gerforce Experience, in all the cases above that boot, I am getting Code 43 after reboot (in some cases before) Threads and Videos I looked at before making this post: How to passthrough an nvidia gpu as primary gpu in unRAID Building a 10 core unRAID server from start to finish - Pt-3 Docker containers and VMs (All parts) The best way to install and setup a windows 10 vm as a daily driver or a Gaming VM VIDEO GUIDE***How to pass through an NVIDIA GPU as primary or only gpu in unRAID [Resolved] Primary GPU passthrough I have also attached my modified rom dump for review. Please let me know if I can provide any other details that will help, and don't hesitate to confirm I followed steps in any of the tutorials above because pebkac is a thing. Thanks for your time, vm.xml unraidHardwareDetails.xml Gigabyte.GTX1070.mini.rom