yellowcooln Posted January 10, 2020 Share Posted January 10, 2020 Hello, I am having a problem when I import my 1050 TI into a Windows 10 VM. I boot it with the GPU black screen and the VM doesn't boot and I can verify that it doesn't boot cause i have TeamViewer installed and RDP configured and it doesn't let me remote in. I force stop the VM and start the VM again and I get error " internal error: Unknown PCI header type '127' for device '0000:08:00.0'" I can't get this error to go away until I reboot unraid. And it does not reboot cleanly, it will freeze and I will have to force reset the box. I have 2 GPU's in the machine so unraid still has a display. I've tired with and without. Here are the specs of the server Mobo: Asus x370-Pro BIOS 5220 RAM: Corsair 32GB of ram 2x16gb CPU: Ryzen 7 1700 GPU: MSI GTX 1050 Ti For VM GPU: PNY 750 Ti for unRAID I saw a thread (here for link) talking about the same thing but with a RX550, but it was old and I wanted to start a new one. Here is my Log for the VM -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 pcie-root-port,port=0xb,chassis=4,id=pci.4,bus=pcie.0,addr=0x1.0x3 \ -device pcie-pci-bridge,id=pci.5,bus=pci.1,addr=0x0 \ -device pcie-root-port,port=0xc,chassis=6,id=pci.6,bus=pcie.0,addr=0x1.0x4 \ -device pcie-root-port,port=0xd,chassis=7,id=pci.7,bus=pcie.0,addr=0x1.0x5 \ -device pcie-root-port,port=0xe,chassis=8,id=pci.8,bus=pcie.0,addr=0x1.0x6 \ -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.3,addr=0x0 \ -drive 'file=/mnt/disks/INTEL_SSDPEDMD400G4D_HHHL_NVMe_400GB_CVFT5035004F400BGN/Windows 10/vdisk1.img,format=raw,if=none,id=drive-virtio-disk2,cache=writeback' \ -device virtio-blk-pci,scsi=off,bus=pci.4,addr=0x0,drive=drive-virtio-disk2,id=virtio-disk2,bootindex=1,write-cache=on \ -drive 'file=/mnt/user/domains/Windows 10/vdisk2.img,format=raw,if=none,id=drive-virtio-disk3,cache=writeback' \ -device virtio-blk-pci,scsi=off,bus=pci.6,addr=0x0,drive=drive-virtio-disk3,id=virtio-disk3,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:e2:ee:18,bus=pci.2,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 usb-tablet,id=input0,bus=usb.0,port=1 \ -device vfio-pci,host=0000:08:00.0,id=hostdev0,bus=pci.7,addr=0x0 \ -device vfio-pci,host=0000:08:00.1,id=hostdev1,bus=pci.8,addr=0x0 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2020-01-10 03:23:14.594+0000: Domain id=2 is tainted: high-privileges 2020-01-10 03:23:14.594+0000: Domain id=2 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2020-01-10T03:23:16.641005Z qemu-system-x86_64: vfio: Unable to power on device, stuck in D3 2020-01-10T03:23:16.646077Z qemu-system-x86_64: vfio: Unable to power on device, stuck in D3 2020-01-10T03:23:17.735403Z qemu-system-x86_64: vfio-pci: Cannot read device rom at 0000:08:00.0 Device option ROM contents are probably invalid (check dmesg). Skip option ROM probe with rombar=0, or load from file with romfile= 2020-01-10T03:24:07.061296Z qemu-system-x86_64: terminating on signal 15 from pid 8040 (/usr/sbin/libvirtd) 2020-01-10 03:24:08.462+0000: shutting down, reason=destroyed 2020-01-10 03:24:23.873+0000: shutting down, reason=failed Here is my 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.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-1fh) PCIe Dummy Host Bridge IOMMU group 3: [1022:1452] 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) 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-1fh) PCIe Dummy Host Bridge IOMMU group 7: [1022:1452] 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) 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-1fh) 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] X370 Series Chipset USB 3.1 xHCI Controller (rev 02) [1022:43b5] 01:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] X370 Series Chipset SATA Controller (rev 02) [1022:43b0] 01:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] X370 Series Chipset PCIe Upstream Port (rev 02) [1022:43b4] 02:00.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) [8086:0953] 03:00.0 Non-Volatile memory controller: Intel Corporation PCIe Data Center SSD (rev 01) [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) IOMMU group 14: [10de:1380] 07:00.0 VGA compatible controller: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] (rev a2) [10de:0fbc] 07:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1) IOMMU group 15: [10de:1c82] 08:00.0 VGA compatible controller: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] (rev ff) [10de:0fb9] 08:00.1 Audio device: NVIDIA Corporation GP107GL High Definition Audio Controller (rev ff) IOMMU group 16: [1022:145a] 09:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function IOMMU group 17: [1022:1456] 09:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor IOMMU group 18: [1022:145c] 09:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) USB 3.0 Host Controller IOMMU group 19: [1022:1455] 0a:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Renoir PCIe Dummy Function IOMMU group 20: [1022:7901] 0a:00.2 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) IOMMU group 21: [1022:1457] 0a:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller Here is the XML for the VM: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows 10</name> <uuid>8b172df4-87ce-ce9a-ff8f-f5638c73f35e</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>6291456</memory> <currentMemory unit='KiB'>6291456</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>16</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='8'/> <vcpupin vcpu='2' cpuset='1'/> <vcpupin vcpu='3' cpuset='9'/> <vcpupin vcpu='4' cpuset='2'/> <vcpupin vcpu='5' cpuset='10'/> <vcpupin vcpu='6' cpuset='3'/> <vcpupin vcpu='7' cpuset='11'/> <vcpupin vcpu='8' cpuset='4'/> <vcpupin vcpu='9' cpuset='12'/> <vcpupin vcpu='10' cpuset='5'/> <vcpupin vcpu='11' cpuset='13'/> <vcpupin vcpu='12' cpuset='6'/> <vcpupin vcpu='13' cpuset='14'/> <vcpupin vcpu='14' cpuset='7'/> <vcpupin vcpu='15' cpuset='15'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-4.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/8b172df4-87ce-ce9a-ff8f-f5638c73f35e_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='16' 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/disks/INTEL_SSDPEDMD400G4D_HHHL_NVMe_400GB_CVFT5035004F400BGN/Windows 10/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Windows 10/vdisk2.img'/> <target dev='hdd' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </disk> <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> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x9'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0xa'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0xb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-to-pci-bridge'> <model name='pcie-pci-bridge'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0xc'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0xd'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/> </controller> <controller type='pci' index='8' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='8' port='0xe'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x6'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:e2:ee:18'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' 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'/> </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> <rom file='/mnt/user/domains/dumps/MSI.GTX1050Ti.4096.160929_1.ROM'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x01' 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='0x05' slot='0x02' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> </domain> I've attached my Diagnostics for the server. Any help would be appreciated. Thanks! unraid-diagnostics-20200109-2240.zip Quote Link to comment
yellowcooln Posted January 19, 2020 Author Share Posted January 19, 2020 I don't normally bump post but I would really like to get this working and I have no clue what is wrong. Quote Link to comment
david279 Posted January 19, 2020 Share Posted January 19, 2020 Update your bios. Go up to a bios that is atleast 1.0.0.4 patch b. A bug was introduced when support for ryzen 3000 was added that killed gpu pass through. Quote Link to comment
yellowcooln Posted January 19, 2020 Author Share Posted January 19, 2020 Just now, david279 said: Update your bios. I am on the newest BIOS, Which at the time of typing this is 5220. 1 minute ago, david279 said: A bug was introduced when support for ryzen 3000 was added that killed gpu pass through. This is probably what happened. I updated to the newest BIOS because I put a 3900x in that mobo before I got a x570 board for my main gaming rig. Looking into downgrading the BIOS for it to work. Quote Link to comment
cjbconnor Posted February 7, 2020 Share Posted February 7, 2020 There's a new beta BIOS floating around that works, I'm using it Quote Link to comment
yellowcooln Posted February 7, 2020 Author Share Posted February 7, 2020 (edited) I was able to get it working by downgrading the motherboard BIOS to 4207. I did it using the guide here on the ROG forums. It was probably the scariest things I've ever done. I made sure I had the server on a UPS just in case. After that I was able to pass through a graphics card into my Windows 10 VM. Edited February 7, 2020 by yellowcooln Spelling 1 Quote Link to comment
pederm Posted April 2, 2020 Share Posted April 2, 2020 (edited) According to sources, a 5406 beta bios exist for Asus x370 boards, which seems to play nice with both Ryzen 3rd gen and virtualization (AGESA 1.0.0.4B). Probably the one that @cjbconnor refers to? I have downloaded it for my x370 Prime, but have not flashed it. Other manufacturers seems to have released this some time ago for their x370 based boards, just not Asus. In case anybody has tried this on an Asus x370 based board, please report results. Edited April 2, 2020 by pederm Mentioning @cjbconner remark Quote Link to comment
Shinobi Posted June 7, 2020 Share Posted June 7, 2020 I understand that Asus X370 BIOS version 5220, surely breaks PCI pass-through support for Ryzen 1st gen CPUs. I too made the mistake of updating to BIOS 5220 in an Asus Prime X370 Pro mobo with a Ryzen 1700X & regret it. Going by release schedules, I find that X370 ROG Crosshair mobos, got their "1.0.0.4 patch b" update on Dec-2019, followed by the update for X370 ROG Strix mobos on Apr-May-2020, after a 4 to 5 month gap, which could mean X370 Prime mobos might get their stable updates by Sep-Oct 2020 in theory. How about Ryzen 2000 & Ryzen 3000 series with an Asus X370 motherboard having BIOS 5220? Is it the same situation with them also with BIOS 5220 ? Do we have any data about that ? Quote Link to comment
yellowcooln Posted June 7, 2020 Author Share Posted June 7, 2020 7 hours ago, Shinobi said: How about Ryzen 2000 & Ryzen 3000 series with an Asus X370 motherboard having BIOS 5220? I was wondering that too. Cause I might want to upgrade the server to a 3900x down the line. Quote Link to comment
Shinobi Posted August 2, 2020 Share Posted August 2, 2020 There is some good news now for the Asus X370 boards!! We've got a new BIOS - Version 5601 - Released on July 27, 2020 🙂 It would be interesting to know if it fixes the PCI passthrough problems Quote Improve system performance Improve DRAM stability Improve system stability Improve system compatibility Fixed AI suite 3 issue Update AM4 AGESA to 1006 Fixed HDMI and DP sound issue Quote Link to comment
yellowcooln Posted August 2, 2020 Author Share Posted August 2, 2020 5 hours ago, Shinobi said: There is some good news now for the Asus X370 boards!! We've got a new BIOS - Version 5601 - Released on July 27, 2020 🙂 It would be interesting to know if it fixes the PCI passthrough problems I might have to do some testing in a bit then. But I really dont want to downgrade my BIOS again if it doesn't work. So I might just leave it for now. If anyone else would like to try please let the thread know. Quote Link to comment
dev2day Posted August 11, 2020 Share Posted August 11, 2020 Found this thread a couple of months ago and finally got my VM hardware passthrough! Had to revert my bios to 4207. They released another bios 5603 on the 8/8/2020. Just wanted to see if anyone else have had success with new bios. Thanks again for this thread! It's been a life saver! Quote Link to comment
yellowcooln Posted December 16, 2020 Author Share Posted December 16, 2020 (edited) Hey guys. Just wondering if anyone has tried 5603 yet? I have yet to update the BIOS because I use hardware passthrough and I'm planning on upgrading the CPU to my old 3900x (5900x hype). And I need to update the bios for the 3900x to work. Edited December 16, 2020 by yellowcooln Quote Link to comment
dev2day Posted January 30, 2021 Share Posted January 30, 2021 On 12/15/2020 at 10:16 PM, yellowcooln said: Hey guys. Just wondering if anyone has tried 5603 yet? I have yet to update the BIOS because I use hardware passthrough and I'm planning on upgrading the CPU to my old 3900x (5900x hype). And I need to update the bios for the 3900x to work. Sorry to revive this thread, but I have good news! I took the dive and updated my bios to 5603 from 4207 and have my passthrough working just fine!!!! I was actually shocked. I believe it is because they updated to AGESA to 1006 in bios version Version 5601 which is the same AGESA as in bios 4207. ( at least that was my thought prosses) Glad they finally released a working bios for passthrough after many years!!!! 2 Quote Link to comment
allroy1975 Posted March 4, 2021 Share Posted March 4, 2021 On 1/29/2021 at 8:02 PM, dev2day said: Sorry to revive this thread, but I have good news! I took the dive and updated my bios to 5603 from 4207 and have my passthrough working just fine!!!! I was actually shocked. I believe it is because they updated to AGESA to 1006 in bios version Version 5601 which is the same AGESA as in bios 4207. ( at least that was my thought prosses) Glad they finally released a working bios for passthrough after many years!!!! i was nervous with only 1 person posting this, but took the plunge this morning and am please to report that i'm also doing pretty well with 5603! Unraid still has an IOMMU group (13 for me) totally locked down...and that group has both of my NICs. I like to pass through a physical NIC to one of my VMs, so that kinda sucks, but....Fix Common Problems says i don't have any problems....so that's pretty sweet....i guess. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.