dodgypast

There's a thread on the level 1 forums about this: https://forum.level1techs.com/t/attention-amd-vfio-users-do-not-update-your-bios/142685/54 I've also been in contact with Gigabyte about it and they're reaching out to AMD. Hopefully your video will raise awareness as there's been quite a few threads about this issue here and on reddit.

I've tested it and it doesn't work for the ax370 board, I would imagine it's the same on the x470 as it's based on the same AGESA.

F25 for the ax370. I saw someone mention F5 working for a x470 gigabyte board.

I just bumped the level 1 tech thread and there's a reply to check back in a couple of weeks but the implication is that x570 boards will work with vfio

further research led me to this link: https://forum.level1techs.com/t/attention-amd-vfio-users-do-not-update-your-bios/142685 It's an AMD issues with the BIOS code they're giving to OEMs. It would be nice to know what the developers are doing to try and get AMD to do something about it... or even acknowledge / warn users that their product cannot perform one of it's heavily advertised features in a significant set of circumstances.

https://forum.level1techs.com/t/attention-amd-vfio-users-do-not-update-your-bios/142685/39 I was researching this error and there doesn't seem to be much awareness on the forums ( including myself up to now ) that this is an issue with the latest AMD BIOSs, this is particularly relevant to anyone planning on upgrading to Ryzen 3000 systems.

Please report this to gigabyte here: https://esupport.gigabyte.com The more who complain the more likely they will test future BIOS on unRAID.

I've just read someone else who got this problem due to a bios update on a gigabyte motherboard and I had to downgrade my bios on a gigabyte motherboard due to the same error so I would guess that's the place to start. Please report this to gigabyte here: https://esupport.gigabyte.com The more who complain the more likely they will test future BIOS on unRAID.

After 2 days of fighting this problem I solved it. I really don't understand how it fixed it, but here are the steps that did: 1. Downloaded the lastest drivers from nvidia ( 430.68 ) using VNC 2. Told Windows to reset itself from recovery using VNC 3. Shut down and swapped to passthrough 4. Booted and installed the latest drivers. Now it's working. I think there might have been a problem with the drivers it downloaded from MS, but I really don't have a clue.

As stated in the title. It works with VNC but crashes as soon as I passthrough the graphics card. Here are the logs from the VM, first with it working with VNC then with it crashing with passthrough. 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-2-Windows 10/master-key.aes' \ -machine pc-i440fx-3.1,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/40837305-fe22-b321-e212-4a24bdd90d0a_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 \ -m 12288 \ -realtime mlock=off \ -smp 12,sockets=1,cores=12,threads=1 \ -uuid 40837305-fe22-b321-e212-4a24bdd90d0a \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=26,server,nowait \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=localtime \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 \ -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x7 \ -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x7.0x1 \ -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x7.0x2 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 \ -device usb-hub,id=hub0,bus=usb.0,port=1 \ -drive 'file=/mnt/user/domains/Windows 10/vdisk1.img,format=raw,if=none,id=drive-virtio-disk2,cache=writeback' \ -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk2,id=virtio-disk2,bootindex=1,write-cache=on \ -drive file=/dev/nvme0n1,format=raw,if=none,id=drive-virtio-disk3,cache=writeback \ -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk3,id=virtio-disk3,write-cache=on \ -netdev tap,fd=28,id=hostnet0,vhost=on,vhostfd=29 \ -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:4b:5a:8c,bus=pci.0,addr=0x3 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0 \ -chardev socket,id=charchannel0,fd=31,server,nowait \ -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -device usb-tablet,id=input0,bus=usb.0,port=1.6 \ -vnc 0.0.0.0:0,websocket=5700 \ -k en-us \ -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2 \ -device usb-host,hostbus=3,hostaddr=2,id=hostdev0,bus=usb.0,port=2 \ -device usb-host,hostbus=5,hostaddr=8,id=hostdev1,bus=usb.0,port=3 \ -device usb-host,hostbus=5,hostaddr=3,id=hostdev2,bus=usb.0,port=4 \ -device usb-host,hostbus=5,hostaddr=4,id=hostdev3,bus=usb.0,port=5 \ -device usb-host,hostbus=5,hostaddr=6,id=hostdev4,bus=usb.0,port=6 \ -device usb-host,hostbus=1,hostaddr=2,id=hostdev5,bus=usb.0,port=1.1 \ -device usb-host,hostbus=1,hostaddr=4,id=hostdev6,bus=usb.0,port=1.2 \ -device usb-host,hostbus=1,hostaddr=3,id=hostdev7,bus=usb.0,port=1.3 \ -device usb-host,hostbus=1,hostaddr=6,id=hostdev8,bus=usb.0,port=1.4 \ -device usb-host,hostbus=5,hostaddr=5,id=hostdev9,bus=usb.0,port=1.5 \ -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2019-06-28 03:50:14.653+0000: Domain id=2 is tainted: high-privileges 2019-06-28 03:50:14.653+0000: Domain id=2 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2019-06-28T03:58:06.751344Z qemu-system-x86_64: terminating on signal 15 from pid 8348 (/usr/sbin/libvirtd) 2019-06-28 03:58:07.385+0000: shutting down, reason=shutdown 2019-06-28 03:59:19.644+0000: starting up libvirt version: 5.1.0, qemu version: 3.1.0, kernel: 4.19.55-Unraid, 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,debug-threads=on' \ -S \ -object 'secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-3-Windows 10/master-key.aes' \ -machine pc-i440fx-3.1,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/40837305-fe22-b321-e212-4a24bdd90d0a_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 \ -m 12288 \ -realtime mlock=off \ -smp 12,sockets=1,cores=12,threads=1 \ -uuid 40837305-fe22-b321-e212-4a24bdd90d0a \ -display none \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=26,server,nowait \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=localtime \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 \ -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x7 \ -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x7.0x1 \ -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x7.0x2 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 \ -device usb-hub,id=hub0,bus=usb.0,port=1 \ -drive 'file=/mnt/user/domains/Windows 10/vdisk1.img,format=raw,if=none,id=drive-virtio-disk2,cache=writeback' \ -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x3,drive=drive-virtio-disk2,id=virtio-disk2,bootindex=1,write-cache=on \ -drive file=/dev/nvme0n1,format=raw,if=none,id=drive-virtio-disk3,cache=writeback \ -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk3,id=virtio-disk3,write-cache=on \ -netdev tap,fd=28,id=hostnet0,vhost=on,vhostfd=29 \ -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:4b:5a:8c,bus=pci.0,addr=0x2 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0 \ -chardev socket,id=charchannel0,fd=31,server,nowait \ -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -device usb-tablet,id=input0,bus=usb.0,port=1.6 \ -device vfio-pci,host=08:00.0,id=hostdev0,bus=pci.0,addr=0x6 \ -device vfio-pci,host=08:00.1,id=hostdev1,bus=pci.0,addr=0x8 \ -device usb-host,hostbus=3,hostaddr=2,id=hostdev2,bus=usb.0,port=2 \ -device usb-host,hostbus=5,hostaddr=8,id=hostdev3,bus=usb.0,port=3 \ -device usb-host,hostbus=5,hostaddr=3,id=hostdev4,bus=usb.0,port=4 \ -device usb-host,hostbus=5,hostaddr=4,id=hostdev5,bus=usb.0,port=5 \ -device usb-host,hostbus=5,hostaddr=6,id=hostdev6,bus=usb.0,port=6 \ -device usb-host,hostbus=1,hostaddr=2,id=hostdev7,bus=usb.0,port=1.1 \ -device usb-host,hostbus=1,hostaddr=4,id=hostdev8,bus=usb.0,port=1.2 \ -device usb-host,hostbus=1,hostaddr=3,id=hostdev9,bus=usb.0,port=1.3 \ -device usb-host,hostbus=1,hostaddr=6,id=hostdev10,bus=usb.0,port=1.4 \ -device usb-host,hostbus=5,hostaddr=5,id=hostdev11,bus=usb.0,port=1.5 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2019-06-28 03:59:19.644+0000: Domain id=3 is tainted: high-privileges 2019-06-28 03:59:19.644+0000: Domain id=3 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2019-06-28T04:00:19.150521Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030 2019-06-28T04:00:19.150754Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030 2019-06-28T04:00:19.151019Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030 2019-06-28T04:00:19.151186Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030 2019-06-28T04:00:19.151344Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030 2019-06-28T04:00:19.151506Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030 2019-06-28T04:00:19.151842Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030 2019-06-28T04:00:19.152021Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030 2019-06-28T04:00:19.152561Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030 2019-06-28T04:00:19.156008Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030 2019-06-28T04:00:19.156273Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030 2019-06-28T04:00:19.156441Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030 2019-06-28T04:00:19.156606Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030 2019-06-28T04:00:19.156778Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030 2019-06-28T04:00:19.157201Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030 2019-06-28T04:00:19.157380Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030 2019-06-28T04:00:19.157942Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030 2019-06-28T04:00:19.161290Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030 2019-06-28T04:00:19.163039Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030 2019-06-28T04:00:19.163217Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030 2019-06-28T04:00:19.163375Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030 2019-06-28T04:00:19.163540Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030 2019-06-28T04:00:19.164013Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030 2019-06-28T04:00:19.164322Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030 2019-06-28T04:00:19.165199Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030 2019-06-28T04:00:19.168919Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030 XML with the graphics card is here: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows 10</name> <uuid>40837305-fe22-b321-e212-4a24bdd90d0a</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>12582912</memory> <currentMemory unit='KiB'>12582912</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>12</vcpu> <cputune> <vcpupin vcpu='0' cpuset='4'/> <vcpupin vcpu='1' cpuset='5'/> <vcpupin vcpu='2' cpuset='6'/> <vcpupin vcpu='3' cpuset='7'/> <vcpupin vcpu='4' cpuset='8'/> <vcpupin vcpu='5' cpuset='9'/> <vcpupin vcpu='6' cpuset='10'/> <vcpupin vcpu='7' cpuset='11'/> <vcpupin vcpu='8' cpuset='12'/> <vcpupin vcpu='9' cpuset='13'/> <vcpupin vcpu='10' cpuset='14'/> <vcpupin vcpu='11' cpuset='15'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-3.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/40837305-fe22-b321-e212-4a24bdd90d0a_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='12' threads='1'/> </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/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </disk> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/nvme0n1'/> <target dev='hdd' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <controller type='pci' index='0' model='pci-root'/> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:4b:5a:8c'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1.6'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x08' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x08' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x045e'/> <product id='0x02e6'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x045e'/> <product id='0x0719'/> </source> <address type='usb' bus='0' port='3'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0x0826'/> </source> <address type='usb' bus='0' port='4'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc226'/> </source> <address type='usb' bus='0' port='5'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc227'/> </source> <address type='usb' bus='0' port='6'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0a12'/> <product id='0x0001'/> </source> <address type='usb' bus='0' port='1.1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1532'/> <product id='0x006c'/> </source> <address type='usb' bus='0' port='1.2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x24ae'/> <product id='0x1005'/> </source> <address type='usb' bus='0' port='1.3'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x264a'/> <product id='0x1fa5'/> </source> <address type='usb' bus='0' port='1.4'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x28de'/> <product id='0x1142'/> </source> <address type='usb' bus='0' port='1.5'/> </hostdev> <hub type='usb'> <address type='usb' bus='0' port='1'/> </hub> <memballoon model='none'/> </devices> </domain> I have also attached my diagnostics. tower-diagnostics-20190628-0419.zip

I've watched that one, but it's used to identify which usb interface the flashdrive is plugged into.... the usb drive is labelled. Looks like I'll have to pass through all the differnt USB interfaces until I find the right one.

The Thermaltake RGB case fans I have plug into a USB header on the motherboard. I'd like to identify and pass through this to Windows so I can control the fans colour using the windows software Thermaltake provide. I have the device info here, but I can't spot anything in itso was hoping someone more knowledgable could help: Bus 1 --> 0000:02:00.0 (IOMMU group 15) Bus 001 Device 004: ID 1532:006c Razer USA, Ltd Bus 001 Device 003: ID 24ae:1005 Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 006: ID 264a:1fa5 Bus 001 Device 005: ID 0424:2512 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 2 --> 0000:02:00.0 (IOMMU group 15) Bus 002 Device 002: ID 0781:5590 SanDisk Corp. Ultra Dual Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 3 --> 0000:04:00.0 (IOMMU group 15) Bus 003 Device 002: ID 045e:02e6 Microsoft Corp. Wireless XBox Controller Dongle Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 4 --> 0000:04:00.0 (IOMMU group 15) Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 5 --> 0000:0a:00.3 (IOMMU group 20) Bus 005 Device 008: ID 045e:0719 Microsoft Corp. Xbox 360 Wireless Adapter Bus 005 Device 005: ID 28de:1142 Bus 005 Device 003: ID 046d:0826 Logitech, Inc. HD Webcam C525 Bus 005 Device 006: ID 046d:c227 Logitech, Inc. G15 Refresh Keyboard Bus 005 Device 004: ID 046d:c226 Logitech, Inc. G15 Refresh Keyboard Bus 005 Device 002: ID 046d:c223 Logitech, Inc. G11/G15 Keyboard / USB Hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 6 --> 0000:0a:00.3 (IOMMU group 20) Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub IOMMU group 17 [RESET] 09:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) 09:00.1 Audio device [0403]: NVIDIA Corporation GP108 High Definition Audio Controller [10de:0fb8] (rev a1) IOMMU group 7 00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] IOMMU group 15 [RESET] 02:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] X370 Series Chipset USB 3.1 xHCI Controller [1022:43b9] (rev 02) 02:00.1 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] X370 Series Chipset SATA Controller [1022:43b5] (rev 02) 02:00.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] X370 Series Chipset PCIe Upstream Port [1022:43b0] (rev 02) [RESET] 03:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02) 03:02.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02) 03:03.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02) 03:04.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02) [RESET] 04:00.0 USB controller [0c03]: ASMedia Technology Inc. ASM1143 USB 3.1 Host Controller [1b21:1343] [RESET] 05:00.0 Ethernet controller [0200]: Intel Corporation I211 Gigabit Network Connection [8086:1539] (rev 03) [RESET] 06:00.0 Ethernet controller [0200]: Qualcomm Atheros Killer E2500 Gigabit Ethernet Controller [1969:e0b1] (rev 10) IOMMU group 5 [RESET] 00:03.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge [1022:1453] IOMMU group 23 0b:00.3 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller [1022:1457] IOMMU group 13 00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0 [1022:1460] 00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1 [1022:1461] 00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2 [1022:1462] 00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3 [1022:1463] 00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4 [1022:1464] 00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5 [1022:1465] 00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 6 [1022:1466] 00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7 [1022:1467] IOMMU group 3 00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] IOMMU group 21 [RESET] 0b:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Renoir PCIe Dummy Function [1022:1455] IOMMU group 11 [RESET] 00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B [1022:1454] IOMMU group 1 [RESET] 00:01.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge [1022:1453] IOMMU group 18 [RESET] 0a:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function [1022:145a] IOMMU group 8 00:07.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] IOMMU group 16 [RESET] 08:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) 08:00.1 Audio device [0403]: NVIDIA Corporation GM204 High Definition Audio Controller [10de:0fbb] (rev a1) IOMMU group 6 [RESET] 00:03.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge [1022:1453] IOMMU group 14 [RESET] 01:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981 [144d:a808] IOMMU group 4 00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] IOMMU group 22 0b:00.2 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51) IOMMU group 12 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 59) 00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51) IOMMU group 2 [RESET] 00:01.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge [1022:1453] IOMMU group 20 [RESET] 0a:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) USB 3.0 Host Controller [1022:145c] IOMMU group 10 00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] IOMMU group 0 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] IOMMU group 19 0a:00.2 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor [1022:1456] IOMMU group 9 [RESET] 00:07.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B [1022:1454]

Downgrading to the gigabyte f 25 BIOS fixed it.

to add some further debugging I tried; I installed a linux VM and got the same error. I then tried passing through my 1030 to the linux VM. The linux VM appeared to start but the monitor went blank ( my GUI was on the 1030 ). Then the linux VM would not stop when the command was sent. After trying to restart the VM on the 1030 graphics card I got the Unknown PCI header type '127' error again. tower-diagnostics-20190625-0732.zip

As the title says I'm getting this error when trying to start the VM with a GTX 970 passed through, it works fine with VNC instead. The most recent log from the VM is: -uuid 7b590d1b-146d-f7c3-5c21-fd29a844e263 \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=26,server,nowait \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=localtime \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 \ -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x7 \ -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x7.0x1 \ -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x7.0x2 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 \ -drive 'file=/mnt/user/domains/Windows 10/vdisk1.img,format=raw,if=none,id=drive-virtio-disk2,cache=writeback' \ -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk2,id=virtio-disk2,bootindex=1,write-cache=on \ -drive file=/mnt/user/isos/Windows.iso,format=raw,if=none,id=drive-ide0-0-0,readonly=on \ -device ide-cd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=2 \ -drive file=/mnt/user/isos/virtio-win-0.1.160-1.iso,format=raw,if=none,id=drive-ide0-0-1,readonly=on \ -device ide-cd,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1 \ -netdev tap,fd=28,id=hostnet0,vhost=on,vhostfd=29 \ -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:d2:4e:b2,bus=pci.0,addr=0x3 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0 \ -chardev socket,id=charchannel0,fd=30,server,nowait \ -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -device usb-tablet,id=input0,bus=usb.0,port=1 \ -vnc 0.0.0.0:0,websocket=5700 \ -k en-us \ -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2 \ -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2019-06-25 05:36:42.928+0000: Domain id=7 is tainted: high-privileges 2019-06-25 05:36:42.928+0000: Domain id=7 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2019-06-25T05:39:07.569031Z qemu-system-x86_64: warning: guest updated active QH 2019-06-25T05:57:37.890302Z qemu-system-x86_64: terminating on signal 15 from pid 10228 (/usr/sbin/libvirtd) 2019-06-25 05:57:38.229+0000: shutting down, reason=shutdown 2019-06-25 05:59:22.255+0000: shutting down, reason=failed My system devices are: PCI Devices and IOMMU Groups IOMMU group 0: [1022:1452] 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) 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-1fh) PCIe Dummy Host Bridge IOMMU group 4: [1022:1452] 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) 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:1453] 00:03.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge IOMMU group 7: [1022:1452] 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 8: [1022:1452] 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 9: [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 10: [1022:1452] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge IOMMU group 11: [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 12: [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 13: [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 14: [144d:a808] 01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981 IOMMU group 15: [1022:43b9] 02:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] X370 Series Chipset USB 3.1 xHCI Controller (rev 02) [1022:43b5] 02:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] X370 Series Chipset SATA Controller (rev 02) [1022:43b0] 02:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] X370 Series Chipset PCIe Upstream Port (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) [1b21:1343] 04:00.0 USB controller: ASMedia Technology Inc. ASM1143 USB 3.1 Host Controller [8086:1539] 05:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03) [1969:e0b1] 06:00.0 Ethernet controller: Qualcomm Atheros Killer E2500 Gigabit Ethernet Controller (rev 10) IOMMU group 16: [10de:13c2] 08:00.0 VGA compatible controller: NVIDIA Corporation GM204 [GeForce GTX 970] (rev ff) [10de:0fbb] 08:00.1 Audio device: NVIDIA Corporation GM204 High Definition Audio Controller (rev ff) IOMMU group 17: [10de:1d01] 09:00.0 VGA compatible controller: NVIDIA Corporation GP108 [GeForce GT 1030] (rev a1) [10de:0fb8] 09:00.1 Audio device: NVIDIA Corporation GP108 High Definition Audio Controller (rev a1) IOMMU group 18: [1022:145a] 0a:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function IOMMU group 19: [1022:1456] 0a:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor IOMMU group 20: [1022:145c] 0a:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) USB 3.0 Host Controller IOMMU group 21: [1022:1455] 0b:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Renoir PCIe Dummy Function IOMMU group 22: [1022:7901] 0b:00.2 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) IOMMU group 23: [1022:1457] 0b:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller CPU Thread Pairings Pair 1: cpu 0 / cpu 8 Pair 2: cpu 1 / cpu 9 Pair 3: cpu 2 / cpu 10 Pair 4: cpu 3 / cpu 11 Pair 5: cpu 4 / cpu 12 Pair 6: cpu 5 / cpu 13 Pair 7: cpu 6 / cpu 14 Pair 8: cpu 7 / cpu 15 USB Devices Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 0781:5590 SanDisk Corp. Ultra Dual Bus 001 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 004: ID 24ae:1005 Bus 001 Device 005: ID 1532:006c Razer USA, Ltd Bus 001 Device 006: ID 0424:2512 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 007: ID 264a:1fa5 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 045e:02e6 Microsoft Corp. Wireless XBox Controller Dongle Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 002: ID 046d:c223 Logitech, Inc. G11/G15 Keyboard / USB Hub Bus 005 Device 003: ID 046d:0826 Logitech, Inc. HD Webcam C525 Bus 005 Device 004: ID 046d:c226 Logitech, Inc. G15 Refresh Keyboard Bus 005 Device 005: ID 28de:1142 Bus 005 Device 006: ID 046d:c227 Logitech, Inc. G15 Refresh Keyboard Bus 005 Device 007: ID 045e:0719 Microsoft Corp. Xbox 360 Wireless Adapter Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub SCSI Devices [0:0:0:0] disk SanDisk Ultra 1.00 /dev/sda 15.3GB [1:0:0:0] disk ATA ST8000AS0002-1NA AR17 /dev/sdb 8.00TB [2:0:0:0] disk ATA ST8000AS0002-1NA AR17 /dev/sdc 8.00TB [3:0:0:0] disk ATA C300-CTFDDAC128M 0002 /dev/sdd 128GB [4:0:0:0] disk ATA ST8000VX0022-2EJ AV01 /dev/sde 8.00TB [5:0:0:0] disk ATA Samsung SSD 850 2B6Q /dev/sdf 250GB [6:0:0:0] disk ATA ST8000AS0002-1NA AR13 /dev/sdg 8.00TB [7:0:0:0] disk ATA ST8000AS0002-1NA AR17 /dev/sdh 8.00TB [8:0:0:0] disk ATA WDC WD60EZRZ-00G 0A80 /dev/sdi 6.00TB [N:0:4:1] disk Samsung SSD 970 EVO Plus 1TB__1 /dev/nvme0n1 1.00TB Unfortunately I don't know how to get the xml for the VM so I've included a picture ( no usb devices are currently passed through ). I have also included my diagnostics.zip tower-diagnostics-20190625-0605.zip

What I'm looking for is advice as to how I want my setup to work: Harware available: 1x128Gb SSD 1x256Gb SSD 1x2Tb ( 7200 RPM ) 1x3Tb ( 7200 RPM ) 1x4Tb ( 5400 RPM ) 5x8Tb ( 4xSeagate Archive drives, 1x 8Tb ) 1xRyzen 1700x, 16Gb RAM, nVidia 970GTX What I want to do: Windows gaming, office and other windows only apps. ( ideally the windows desktop would be the interface I use to manage it ) Download and seed huge quantities of torrents over VPN Run Plex (not over VPN ) / Sonarr / Jackett, Ombi is a plus. How would I go about making the best of my hardware to meet my goals.