killeriq

well it can be Media server and desktop also did the same...thats why all those try/fails with GPU pass-through - the HEX mod is easy few mins to mod it... How do u want to mine? create Linux VM with nvOC or something like that and let it run? ...minig my my original idea...but 3 card do lot of heat, so ive put 12x 1080ti on water into Rig

So other issue on windows START button stopped to work and behaved strange - seems like more people with this issue and here is the fix: http://home.bt.com/tech-gadgets/computing/windows-10/has-your-windows-10-start-menu-stopped-working-here-are-four-ways-to-fix-it-11364000314532 Original answer: 1- Right click on start menu and click on Run. "For those who the start menu does not respond with right click, right click on taskbar - click on Task Manager - from File menu on the left upper corner select Run new task". 2- Write the command regedit and click Enter. 3- Go to path [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WpnUserService]. 4- Double click on Start from the right side. 5- Change the value data to 4 then OK. 6- Reboot.

so ur using the "rom dump file" right? Yeah i have the same issue with UEFI spend couple of days on that till i find it out

Which GPU do you use and do you have UEFI enabled or disabled on Unraid Flash USB?

Got into one more issue with Rights, when im trying to set/move folder on the NAS it say it doesnt have permissions, its set on Public (unraid) and i can create/edit folders in TotalCommander and Explorer so no clue where is it blocked again Thanks EDIT: Also how do i get the "UNRAID NAS" to be listed under network ? It shows other PC on network , but when im trying to seach through i need to manually enter \\unraid\ Tried this solution , but didnt helped

Works!!! maan thanks after a week of trying GPU thing - this went pretty fast thanks to you Thanks so much , finally i can go further with my All in ONE machine setup

Only this Win10 VM...rest is fine, but as you can see VM can see devices on the network except Unraid shares

well seems like Win10 is not able to see or connect to the Unraid at all, i see just other devices on network. when i type \\unraidtower or \\192.168.x.xx get just error - same stuff work from my laptop

Ok seems like i found the root cause: When i set USB flash (unraid) to boot as UEFI - it gives this error and GPU passthrou is not working at all, soon as i disable GPU works fine.... --- But now im facing other problem Win VM cant see unraid shares, im able to see devices on network , but not shares even when i type manually address - which work from other devices... This is never ending

having the same on VM Win10 running on Unraid im not able to see "unraid" shares even when i put \\unraidname or \\unraidIP Other devices on my network are visible...even on Dockers im able to see shares...

Seems like there in an issue with the OS it self im using, tried other USD with new install and its working right away

Tried to set fresh unraid on other USB...and after i added dumped rom file into XML is working as 1st GPU on first try... ...so probably is something messed in the OS i use, not sure what is it...but probably need to swich to new to get it working, strange EDIT: Nvidia GPU - needs rom dump file into XML AMD GPU - works without dump file EDIT2: The error is caused by UEFI FLASH (unraid) boot setting - soon as i enable im not able to pass the GPU, when i disable the UEFI again , it wont start. Could someone try that? Main -> Boot Device -> FLASH (click on that) Also the error is gone in this - im on 6.4.0 Stable now...will do more tests on those RC if i would be able to update 2018-01-14T12:35:57.822108Z qemu-system-x86_64: -device vfio-pci,host=0a:00.0,id=hostdev0,bus=pci.0,addr=0x6: Failed to mmap 0000:0a:00.0 BAR 3. Performance may be slow new log: 2018-01-14 13:37:22.515+0000: starting up libvirt version: 3.8.0, qemu version: 2.10.2, hostname: Tower LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'guest=Windows 10 - 2,debug-threads=on' -S -object 'secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-5-Windows 10 - 2/master-key.aes' -machine pc-i440fx-2.10,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/4a9a652f-26e6-4784-af39-8e7859fdb734_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 12288 -realtime mlock=off -smp 8,sockets=1,cores=8,threads=1 -uuid 4a9a652f-26e6-4784-af39-8e7859fdb734 -display none -no-user-config -nodefaults -chardev 'socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-5-Windows 10 - 2/monitor.sock,server,nowait' -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=o070mini-mod.dump -device vfio-pci,host=0a:00.1,id=hostdev1,bus=pci.0,addr=0x6 -device vfio-pci,host=0c:00.3,id=hostdev2,bus=pci.0,addr=0x8 -device usb-host,hostbus=5,hostaddr=6,id=hostdev3,bus=usb.0,port=1 -device usb-host,hostbus=5,hostaddr=4,id=hostdev4,bus=usb.0,port=2 -device usb-host,hostbus=5,hostaddr=5,id=hostdev5,bus=usb.0,port=3 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x9 -msg timestamp=on 2018-01-14 13:37:22.515+0000: Domain id=5 is tainted: high-privileges 2018-01-14 13:37:22.515+0000: Domain id=5 is tainted: host-cpu 2018-01-14T13:37:22.577346Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0) 2018-01-14T13:37:24.088519Z qemu-system-x86_64: vfio: Cannot reset device 0000:0c:00.3, depends on group 19 which is not owned. 2018-01-14T13:37:25.122666Z qemu-system-x86_64: vfio: Cannot reset device 0000:0c:00.3, depends on group 19 which is not owned. 2018-01-14T13:37:38.193091Z qemu-system-x86_64: libusb_release_interface: -4 [NO_DEVICE] 2018-01-14T13:37:38.193115Z qemu-system-x86_64: libusb_release_interface: -4 [NO_DEVICE] libusb: error [udev_hotplug_event] ignoring udev action bind

even with GTX 1070 still no luck ...group 19 has only 1 device so dont know why i get this error 2018-01-14 12:35:56.281+0000: starting up libvirt version: 3.8.0, qemu version: 2.10.2, hostname: unRAIDTower LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'guest=Windows 10 - 2,debug-threads=on' -S -object 'secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-1-Windows 10 - 2/master-key.aes' -machine pc-i440fx-2.10,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/4a9a652f-26e6-4784-af39-8e7859fdb734_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 12288 -realtime mlock=off -smp 8,sockets=1,cores=8,threads=1 -uuid 4a9a652f-26e6-4784-af39-8e7859fdb734 -no-user-config -nodefaults -chardev 'socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-1-Windows 10 - 2/monitor.sock,server,nowait' -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device nec-video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2 -device vfio-pci,host=0a:00.0,id=hostdev0,bus=pci.0,addr=0x6 -device vfio-pci,host=0a:00.1,id=hostdev1,bus=pci.0,addr=0x8 -device vfio-pci,host=0c:00.3,id=hostdev2,bus=pci.0,addr=0x9 -device usb-host,hostbus=5,hostaddr=5,id=hostdev3,bus=usb.0,port=1 -device usb-host,hostbus=5,hostaddr=3,id=hostdev4,bus=usb.0,port=2 -device usb-host,hostbus=5,hostaddr=4,id=hostdev5,bus=usb.0,port=3 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0xa -msg timestamp=on 2018-01-14 12:35:56.281+0000: Domain id=1 is tainted: high-privileges 2018-01-14 12:35:56.282+0000: Domain id=1 is tainted: host-cpu 2018-01-14T12:35:56.335861Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0) 2018-01-14T12:35:57.822108Z qemu-system-x86_64: -device vfio-pci,host=0a:00.0,id=hostdev0,bus=pci.0,addr=0x6: Failed to mmap 0000:0a:00.0 BAR 3. Performance may be slow 2018-01-14T12:35:57.999447Z qemu-system-x86_64: vfio: Cannot reset device 0000:0c:00.3, depends on group 19 which is not owned. 2018-01-14T12:35:59.061687Z qemu-system-x86_64: vfio: Cannot reset device 0000:0c:00.3, depends on group 19 which is not owned. Here are groups with ACS enabled IOMMU group 0: [1022:1452] 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 1: [1022:1453] 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge IOMMU group 2: [1022:1453] 00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge IOMMU group 3: [1022:1452] 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 4: [1022:1452] 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 5: [1022:1453] 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge IOMMU group 6: [1022:1452] 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 7: [1022:1452] 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 8: [1022:1454] 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B IOMMU group 9: [1022:1452] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 10: [1022:1454] 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B IOMMU group 11: [1022:790b] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 59) [1022:790e] 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) IOMMU group 12: [1022:1460] 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0 [1022:1461] 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1 [1022:1462] 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2 [1022:1463] 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3 [1022:1464] 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4 [1022:1465] 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5 [1022:1466] 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric Device 18h Function 6 [1022:1467] 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7 IOMMU group 13: [144d:a804] 01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961 IOMMU group 14: [1022:43b9] 02:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Device 43b9 (rev 02) [1022:43b5] 02:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] Device 43b5 (rev 02) [1022:43b0] 02:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43b0 (rev 02) [1022:43b4] 03:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 03:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 03:03.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 03:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 03:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 03:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1b21:1343] 07:00.0 USB controller: ASMedia Technology Inc. Device 1343 [8086:1539] 08:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03) IOMMU group 15: [10de:1b81] 0a:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1070] (rev a1) [10de:10f0] 0a:00.1 Audio device: NVIDIA Corporation GP104 High Definition Audio Controller (rev a1) IOMMU group 16: [1022:145a] 0b:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device 145a IOMMU group 17: [1022:1456] 0b:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor IOMMU group 18: [1022:145c] 0b:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) USB 3.0 Host Controller IOMMU group 19: [1022:1455] 0c:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device 1455 IOMMU group 20: [1022:7901] 0c:00.2 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) IOMMU group 21: [1022:1457] 0c:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller

So i had still problem to instal it via OVMF so solve it this way Even now its Win10 installed with OVMF/UEFI the card passthrough doesnt work with AMD R7 250x, so will try again with GTX 1070...start to drive me mad when i have to take all HDD from 1 tower to another... I ming try to dl fresh need Unraid and start from there...

Gridrunner - i was following you video with Win10 install but seems like u had some "better" iso then me... Had same issue ISO which working on SeaBIOS, is giving me the command line. "FS0:" is not working...so i had to use "Rufus" to create UEFI bootable USB Drive and then passthrough it into VM to be able to start the installation... After i passed USB i was able to enter "FS0:" and start installation.... --- Now trying again to pass GPU and still not working but i moved a bit i guess...

Had Gigabyte Gaming K5 - Bios is crap comparing to Asus, 2nd LAN port wasnt working in Unraid (not even light when i attach cable). And after like 2 days of usage didnt booted up...i was also confused with the Bios switches. Thought it would be great board with the 2x LAN and LED panel for error codes , but in the end i return it and got Asus X370-Pro (will might switch it to Asus Crosshair VI due to 3200Mhz RAM support). It might have been problematic piece, no clue...but Red Bios was define-telly not my cup of coffe

About your "freezing" issue try this fix (command value) into the kernel, fo me it help to prevent freezing https://youtu.be/T_BmK9vSjPA?t=583 My issue: I have the same board as you. unRAID OS version 6.4.0-rc19b Asus X370-Pro (bios also latest) Ryzen 1700 G.SKILL 32GB KIT DDR4 3200MHz CL14 Trident Z (GSKILL0014) (on 3066, not running 3200Mhz on this board) Sapphire Radeon R7 250x ZOTAC GeForce GTX 1070 Mini - 10pcs (so i dont think its an card issue). To install Win10 VM i had to switch into "SeaBios" as OVMF wasnt working...maybe this could be the problem , which setting do you have? Win10 is installed i can run it with VNC as primary and GPU as 2nd card-has LCD screen out, but soon as ive set GPU as primary (Amd or Nvidia), even with that "dump bios" it wont work...just get black screen, sometime blinking cursor or monitor goes to stand by. As ive posted in other thread i get this error in VM log Thanks

Guys, does anybody using Ryzen build as VM with Primary GPU passthrough (u can see Win10 on monitor - without VNC) ? Been trying few days with different combinations of GPU (2x 1070 and Radeon R7 250x) no success , soon as i set it as 1st card even with bios , i get just black screen and sometimes with blinking cursor Wanted to have all in one server , but had to put all HDDs into my ITX machine again Thanks

any help? thx

ACS enabled even tried this : but there is a problem with 2nd card Log

Thanks for the bios dump - but the same monitor which shows normally boot screen/ unraid login and stuff in TXT mode - turns OFF soon as i start the Win10 VM with linked DUMP file. I assume my dump is right as i have 10x Zotac 1070 cards , so should be done right. Cards have their own group even without Enable PCIe ACS Override:set to NO IOMMU group 0: [1022:1452] 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 1: [1022:1453] 00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge IOMMU group 2: [1022:1452] 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 3: [1022:1452] 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 4: [1022:1453] 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge IOMMU group 5: [1022:1453] 00:03.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge IOMMU group 6: [1022:1452] 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 7: [1022:1452] 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 8: [1022:1454] 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B IOMMU group 9: [1022:1452] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 10: [1022:1454] 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B IOMMU group 11: [1022:790b] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 59) [1022:790e] 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) IOMMU group 12: [1022:1460] 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0 [1022:1461] 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1 [1022:1462] 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2 [1022:1463] 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3 [1022:1464] 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4 [1022:1465] 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5 [1022:1466] 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric Device 18h Function 6 [1022:1467] 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7 IOMMU group 13: [1022:43b9] 01:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Device 43b9 (rev 02) [1022:43b5] 01:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] Device 43b5 (rev 02) [1022:43b0] 01:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43b0 (rev 02) [1022:43b4] 02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 02:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 02:03.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 02:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 02:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 02:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1b21:1343] 06:00.0 USB controller: ASMedia Technology Inc. Device 1343 [8086:1539] 07:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03) IOMMU group 14: [10de:1b81] 09:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1070] (rev a1) [10de:10f0] 09:00.1 Audio device: NVIDIA Corporation GP104 High Definition Audio Controller (rev a1) IOMMU group 15: [10de:1b81] 0a:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1070] (rev a1) [10de:10f0] 0a:00.1 Audio device: NVIDIA Corporation GP104 High Definition Audio Controller (rev a1) IOMMU group 16: [1022:145a] 0b:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device 145a IOMMU group 17: [1022:1456] 0b:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor IOMMU group 18: [1022:145c] 0b:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) USB 3.0 Host Controller IOMMU group 19: [1022:1455] 0c:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device 1455 IOMMU group 20: [1022:7901] 0c:00.2 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) IOMMU group 21: [1022:1457] 0c:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller This setup with 2 cards (2card1070a.xml) This is what im getting in the VM LOG: 2018-01-01T23:41:56.045938Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region3+0x124c830, 0xff000000ff000000,8) failed: Device or resource busy 2018-01-01T23:41:56.045958Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region3+0x124c838, 0x0,1) failed: Device or resource busy 2018-01-01T23:41:56.045978Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region3+0x124c839, 0x0,1) failed: Device or resource busy 2018-01-01T23:41:56.045997Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region3+0x124c83a, 0x0,1) failed: Device or resource busy 2018-01-01T23:41:56.046017Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region3+0x124c83b, 0xff,1) failed: Device or resource busy 2018-01-01T23:41:56.046037Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region3+0x124d7c4, 0xff000000,4) failed: Device or resource busy 2018-01-01T23:41:56.046048Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region3+0x124d7c8, 0xff000000,4) failed: Device or resource busy 2018-01-01T23:41:56.046062Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region3+0x124d7cc, 0xff000000,4) failed: Device or resource busy 2018-01-01T23:41:56.046073Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region3+0x124d7d0, 0xff000000,4) failed: Device or resource busy 2018-01-01T23:41:56.046093Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region3+0x124d7d0, 0xff000000ff000000,8) failed: Device or resource busy 2018-01-01T23:41:56.046108Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region3+0x124d7d8, 0xff2f2f2fff000000,8) failed: Device or resource busy 2018-01-01T23:41:56.046128Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region3+0x124d7e0, 0xff9f9f9fffafafaf,8) failed: Device or resource busy 2018-01-01T23:41:56.046143Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region3+0x124d7e8, 0xff000000ff0f0f0f,8) failed: Device or resource busy 2018-01-01T23:41:56.046163Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region3+0x124d7f0, 0xff000000ff000000,8) failed: Device or resource busy 2018-01-01T23:41:56.046178Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region3+0x124d7f8, 0xff000000ff000000,8) failed: Device or resource busy 2018-01-01T23:41:56.046198Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region3+0x124d800, 0xff000000ff000000,8) failed: Device or resource busy 2018-01-01T23:41:56.046213Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region3+0x124d808, 0xff000000ff000000,8) failed: Device or resource busy 2018-01-01T23:41:56.046233Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region3+0x124d810, 0xff000000ff000000,8) failed: Device or resource busy 2018-01-01T23:41:56.046248Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region3+0x124d818, 0xff000000ff000000,8) failed: Device or resource busy 2018-01-01T23:41:56.046268Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region3+0x124d820, 0xff000000ff000000,8) failed: Device or resource busy 2018-01-01T23:41:56.046283Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region3+0x124d828, 0xff000000ff000000,8) failed: Device or resource busy 2018-01-01T23:41:56.046303Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region3+0x124d830, 0xff000000ff000000,8) failed: Device or resource busy 2018-01-01T23:41:56.046323Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region3+0x124d838, 0x0,1) failed: Device or resource busy 2018-01-01T23:41:56.046344Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region3+0x124d839, 0x0,1) failed: Device or resource busy 2018-01-01T23:41:56.046364Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region3+0x124d83a, 0x0,1) failed: Device or resource busy 2018-01-01T23:41:56.046383Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region3+0x124d83b, 0xff,1) failed: Device or resource busy 2018-01-01T23:41:56.046404Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region3+0x124e7c4, 0xff000000,4) failed: Device or resource busy 2018-01-01T23:41:56.046414Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region3+0x124e7c8, 0xff000000,4) failed: Device or resource busy 2018-01-01T23:41:56.046429Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region3+0x124e7cc, 0xff000000,4) failed: Device or resource busy 2018-01-01T23:41:56.046439Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region3+0x124e7d0, 0xff000000,4) failed: Device or resource busy 2018-01-01T23:41:56.046459Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region3+0x124e7d0, 0xff000000ff000000,8) failed: Device or resource busy 2018-01-01T23:41:56.046474Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region3+0x124e7d8, 0xffdfdfdfff000000,8) failed: Device or resource busy 2018-01-01T23:41:56.046494Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region3+0x124e7e0, 0xffffffffffffffff,8) failed: Device or resource busy 2018-01-01T23:41:56.046509Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region3+0x124e7e8, 0xff000000ff9f9f9f,8) failed: Device or resource busy 2018-01-01T23:41:56.046529Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region3+0x124e7f0, 0xff000000ff000000,8) failed: Device or resource busy 2018-01-01T23:41:56.046544Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region3+0x124e7f8, 0xff000000ff000000,8) failed: Device or resource busy 2018-01-01T23:41:56.046595Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region3+0x124e800, 0xff000000ff000000,8) failed: Device or resource busy 2018-01-01T23:41:56.046612Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region3+0x124e808, 0xff000000ff000000,8) failed: Device or resource busy 2018-01-01T23:41:56.046633Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region3+0x124e810, 0xff000000ff000000,8) failed: Device or resource busy 2card1070a.xml Zotac1070mini.rom Zotac1070mini-mod.dump

Hello, Ive just spend like 5h trying to get the card working via bios dump (both guides old with dump via ssh and the new from GPU-Z or Webpage download) and im not able to get picture out of HDMI port to monitor. I have 2x 1070 cards when i set 1st card in the 1st MB slot it wont work, when i set the 2nd card in 2nd MB slot it works and i get picture on monitor... Is there any way how i get it working on 1st one please? Thanks

aah i had it still as plugin...not as docker thx

whats the difference between this one and the Or just 2 releases of the same version? thx