Help With GPU Passthrough after System Upgrade


19 posts in this topic Last Reply

Recommended Posts

Unraid 6.9.0-RC2

CPU: Ryzen 7 3700X

Motherboard: ASUS Prime X570-P

RAM: 32GB

Primary GPU: Radeon RX 5600XT

Secondary GPU: NVIDIA GTX 745

VM: WIndows 10

 

I recently upgraded to a Ryzen 7 3700X, which included a motherboard upgrade (ASUS Prime X570-P) and a RAM upgrade. The upgrade seemed to go without any problems, however I am no longer able to start my Windows 10 VM with a gpu passed through. I have a RX 5600XT that I passthrough and an old NVIDIA gpu I use for transcoding. I am aware of the reset bug present in 5600XT, but this seems to be a separate issue since now when I start  the windows 10 vm I see the TianoCore boot screen, then nothing happens for a while, then white pixels appear all over the screen.

 

I checked IOMMU groups since upgrading and the GPU is in it own group and have tried to run the VM with only the GPU passed through with no luck. I have a vBios I dumped from the card added. I have attached diagnostics from a fresh reboot and running the VM once until the pixelation occurred, then forced stopped it after that.

 

Passing through the NVIDIA GPU works without issue so it seems to be specific to the 5600XT. I came from an intel CPU which had a iGPU so it may have to do with the 5600XT being the primary gpu.

 

If there is any additional information needed let me known. Before upgrading the hardware everything was working perfectly so I'm really at a loss as to what else I should try.

IOMMU group 0:				[1022:1482] 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
IOMMU group 1:				[1022:1483] 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
IOMMU group 2:				[1022:1482] 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
IOMMU group 3:				[1022:1482] 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
IOMMU group 4:				[1022:1483] 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
IOMMU group 5:				[1022:1482] 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
IOMMU group 6:				[1022:1482] 00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
IOMMU group 7:				[1022:1482] 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
IOMMU group 8:				[1022:1484] 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]
IOMMU group 9:				[1022:1482] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
IOMMU group 10:				[1022:1484] 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]
IOMMU group 11:			 	[1022:790b] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61)
			 	[1022:790e] 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
IOMMU group 12:				[1022:1440] 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 0
				[1022:1441] 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 1
				[1022:1442] 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 2
				[1022:1443] 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 3
				[1022:1444] 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 4
				[1022:1445] 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 5
				[1022:1446] 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 6
				[1022:1447] 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 7
IOMMU group 13:				[1022:57ad] 01:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse Switch Upstream
IOMMU group 14:				[1022:57a3] 02:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
IOMMU group 15:				[1022:57a3] 02:03.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
IOMMU group 16:				[1022:57a3] 02:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
IOMMU group 17:				[1022:57a3] 02:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
IOMMU group 18:				[1022:57a4] 02:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
			 	[1022:1485] 07:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP
			 	[1022:149c] 07:00.1 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
				Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
				Bus 003 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
				Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
			 	[1022:149c] 07:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
				Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
				Bus 005 Device 002: ID 0b05:18f3 ASUSTek Computer, Inc. AURA LED Controller
				Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
IOMMU group 19:				[1022:57a4] 02:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
			 	[1022:7901] 08:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
				[7:0:0:0]    disk    ATA      WDC WD10EZEX-08W 1A02  /dev/sdf   1.00TB
				[8:0:0:0]    disk    ATA      WDC WD3200AAJS-6 3A01  /dev/sdg    320GB
IOMMU group 20:				[1022:57a4] 02:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
			 	[1022:7901] 09:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
				[9:0:0:0]    disk    ATA      WDC  WDS500G2B0A 20WD  /dev/sdh    500GB
				[10:0:0:0]   disk    ATA      KINGSTON SV300S3 BBF0  /dev/sdi    120GB
				[13:0:0:0]   disk    ATA      WDC WD1003FZEX-0 1A01  /dev/sdj   1.00TB
				[14:0:0:0]   disk    ATA      ST1000DM003-1ER1 CC45  /dev/sdk   1.00TB
IOMMU group 21:			 	[10de:1382] 03:00.0 VGA compatible controller: NVIDIA Corporation GM107 [GeForce GTX 745] (rev a2)
			 	[10de:0fbc] 03:00.1 Audio device: NVIDIA Corporation GM107 High Definition Audio Controller [GeForce 940MX] (rev a1)
IOMMU group 22:			 	[1b4b:9215] 04:00.0 SATA controller: Marvell Technology Group Ltd. Device 9215 (rev 11)
				[3:0:0:0]    disk    ATA      WDC WD3200AAJS-0 3A01  /dev/sdb    320GB
				[4:0:0:0]    disk    ATA      WDC WD20EZRZ-22Z 0A80  /dev/sdc   2.00TB
				[4:1:0:0]    disk    ATA      ST2000DM008-2FR1 0001  /dev/sdd   2.00TB
				[4:2:0:0]    disk    ATA      ST500LM000-1EJ16 DEM6  /dev/sde    500GB
IOMMU group 23:			 	[1912:0014] 05:00.0 USB controller: Renesas Technology Corp. uPD720201 USB 3.0 Host Controller (rev 03)
				Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
				Bus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
				Bus 001 Device 003: ID 0bda:5411 Realtek Semiconductor Corp. 4-Port USB 2.0 Hub
				Bus 001 Device 004: ID 1b1c:1b5e Corsair CORSAIR HARPOON RGB WIRELESS Gaming Mouse
				Bus 001 Device 005: ID 0458:6006 KYE Systems Corp. (Mouse Systems) PC-LM1E Camera
				Bus 001 Device 006: ID 0bda:8771 Realtek Semiconductor Corp. Bluetooth Radio
				Bus 001 Device 007: ID 046d:c336 Logitech, Inc. Gaming Keyboard G213
				Bus 001 Device 008: ID 0d8c:0014 C-Media Electronics, Inc. USB Audio Device
				Bus 001 Device 009: ID 1b1c:1b65 Corsair CORSAIR HARPOON RGB WIRELESS Gaming Dongle
				Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
				Bus 002 Device 002: ID 0bda:0411 Realtek Semiconductor Corp. 4-Port USB 3.0 Hub
IOMMU group 24:			 	[10ec:8168] 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
IOMMU group 25:				[1002:1478] 0a:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Upstream Port of PCI Express Switch (rev ca)
IOMMU group 26:				[1002:1479] 0b:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Downstream Port of PCI Express Switch
IOMMU group 27:			 	[1002:731f] 0c:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] (rev ca)
IOMMU group 28:			 	[1002:ab38] 0c:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 HDMI Audio
IOMMU group 29:			 	[1022:148a] 0d:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function
IOMMU group 30:			 	[1022:1485] 0e:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP
IOMMU group 31:			 	[1022:1486] 0e:00.1 Encryption controller: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP
IOMMU group 32:			 	[1022:149c] 0e:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
				Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
				Bus 007 Device 002: ID 0461:0010 Primax Electronics, Ltd HP PR1101U / Primax PMX-KPR1101U Keyboard
				Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
				Bus 008 Device 002: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive
IOMMU group 33:			 	[1022:1487] 0e:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller
<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm'>
  <name>Windows10</name>
  <uuid>7dd7d6e6-e24b-6504-2d0c-368bc8bbbc7f</uuid>
  <metadata>
    <vmtemplate xmlns="unraid" name="Windows 10" icon="Win10_Radeon.png" os="windows10"/>
  </metadata>
  <memory unit='KiB'>16777216</memory>
  <currentMemory unit='KiB'>16777216</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>10</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='3'/>
    <vcpupin vcpu='1' cpuset='11'/>
    <vcpupin vcpu='2' cpuset='4'/>
    <vcpupin vcpu='3' cpuset='12'/>
    <vcpupin vcpu='4' cpuset='5'/>
    <vcpupin vcpu='5' cpuset='13'/>
    <vcpupin vcpu='6' cpuset='6'/>
    <vcpupin vcpu='7' cpuset='14'/>
    <vcpupin vcpu='8' cpuset='7'/>
    <vcpupin vcpu='9' cpuset='15'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-q35-5.1'>hvm</type>
    <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
    <nvram>/etc/libvirt/qemu/nvram/7dd7d6e6-e24b-6504-2d0c-368bc8bbbc7f_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' migratable='on'>
    <topology sockets='1' dies='1' cores='5' threads='2'/>
    <cache mode='passthrough'/>
    <feature policy='require' name='topoext'/>
  </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/Windows10/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/Windows10/vdisk2.img'/>
      <target dev='hdd' bus='virtio'/>
      <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/isos/virtio-win-0.1.190-1.iso'/>
      <target dev='hdb' bus='sata'/>
      <readonly/>
      <address type='drive' controller='0' bus='0' target='0' unit='1'/>
    </disk>
    <controller type='usb' index='0' model='nec-xhci' ports='15'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
    </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-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='5' port='0xc'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/>
    </controller>
    <controller type='pci' index='6' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='6' port='0xd'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/>
    </controller>
    <controller type='pci' index='7' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='7' port='0xe'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x6'/>
    </controller>
    <controller type='pci' index='8' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='8' port='0xf'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x7'/>
    </controller>
    <controller type='pci' index='9' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='9' port='0x10'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/>
    </controller>
    <controller type='pci' index='10' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='10' port='0x11'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/>
    </controller>
    <controller type='pci' index='11' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='11' port='0x12'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/>
    </controller>
    <controller type='pci' index='12' model='pcie-to-pci-bridge'>
      <model name='pcie-pci-bridge'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x02' 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:be:07:cc'/>
      <source bridge='br0'/>
      <model type='virtio-net'/>
      <address type='pci' domain='0x0000' bus='0x03' 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='0x0c' slot='0x00' function='0x0'/>
      </source>
      <rom file='/mnt/user/isos/vbios/Navi 10.rom'/>
      <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x0c' slot='0x00' function='0x1'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/>
    </hostdev>
    <memballoon model='none'/>
  </devices>
</domain>

 

20210106_171614.jpg

nateserver-diagnostics-20210106-1711.zip

Edited by ndetar
Link to post
2 minutes ago, jonathanm said:

Are you running your RAM at the speed specced by your processor and the density of the chips? It seems most motherboards try to default the RAM way overclocked in many instances.

If it is the default for motherboards is to overclock, probably. I only changed virtualization and IOMMU settings. Let me check.

Link to post
Just now, jonathanm said:

Yes, you find your processor and cross reference the supported memory frequency.

OK thanks.

 

BIOs is up to date, and I have adjusted to the recommended settings however the problem is still present. I also just noticed I didn't mention that Unraid does not crash, and continues to run no problem.

Link to post
3 minutes ago, ndetar said:

BIOs is up to date, and I have adjusted to the recommended settings however the problem is still present. I also just noticed I didn't mention that Unraid does not crash, and continues to run no problem.

My hunch was based on the video corruption, so my next guess would involve the video BIOS you dumped. What happens if you start the VM without the vbios specified?

Link to post

The same thing. I think the video corruption might actually be incorrectly displayed console text, but i'm not completly sure. I recently noticed that if I hit enter or type the pixelation shifts.

Link to post
19 minutes ago, jonathanm said:

My hunch was based on the video corruption, so my next guess would involve the video BIOS you dumped. What happens if you start the VM without the vbios specified?

 

15 minutes ago, ndetar said:

The same thing. I think the video corruption might actually be incorrectly displayed console text, but i'm not completly sure. I recently noticed that if I hit enter or type the pixelation shifts.

Additionally the last time I rebooted the pixelation started shift up the screen like it was just incorrectly rendering the console reboot text.

Link to post
Posted (edited)

So, strange stuff has happened. For some reason my server isn't logging anything, no idea why I'll have to figure that out later.

 

I decided to create a new unraid usb. Kinda start from scratch. I started a vm with the 5600XT passed through and the system log was filled up with:

unraid kernel: vfio-pci 0000:0c:00.0: BAR 0: can't reserve [mem 0xd0000000-0xdfffffff 64bit pref]

Which lead me to this thread: https://forums.unraid.net/topic/77241-unable-to-passthrough-primary-gpu/

Which recommended running the following commands:

echo 0 > /sys/class/vtconsole/vtcon0/bind
echo 0 > /sys/class/vtconsole/vtcon1/bind
echo efi-framebuffer.0 > /sys/bus/platform/drivers/efi-framebuffer/unbind

After running those commands on a fresh reboot the VM started up with no problem. So I switched back to my original usb drive and ran the same commands before starting the vm and it started right up.

 

I honestly don't know what those commands do so if there is some other more proper fix/solution or an explanation as to what those commands do I'd be very appreciative.

Edited by ndetar
Link to post
3 hours ago, ndetar said:

I honestly don't know what those commands do

They reset the gpu (commands unhook unraid from the gpu, so it can be properly passed through to the vm), search for amd reset bug.

Edited by ghost82
Link to post
8 hours ago, ghost82 said:

They reset the gpu (commands unhook unraid from the gpu, so it can be properly passed through to the vm), search for amd reset bug.

I am aware of the reset bug, had to deal with it before switching hardware, however I didn't have to use those commands before. Is this due to Unraid binding to the 5600XT where as before Unraid would bind to the intel iGPU?

Link to post
17 minutes ago, ndetar said:

Is this due to Unraid binding to the 5600XT where as before Unraid would bind to the intel iGPU?

I think so, because from what you write you can see unraid is binding to the 5600xt, if you want to use igpu set it in the bios as the primary gpu and use vfio for attaching the 5600xt.

However you will not get rid of the reset bug if you will use the 5600xt for your vm(s), but I think you already know what I'm talking about, unless you use some "tricks" to reset the card after shutting down/rebooting the vm.

Edited by ghost82
Link to post
1 minute ago, ghost82 said:

I think so, because from what you write you can see unraid is binding to the 5600xt, if you want to use igpu set it in the bios as the primary gpu and use vfio for attaching the 5600xt.

However you will not get rid of the reset bug if you will use the 5600xt for your vm(s), unless you use some "tricks" to reset the card after shutting down/rebooting the vm.

Well since I switched to the 3700X I no longer have an igpu. I have a secondary NVIDIA gpu, is there any way to get unraid to bind to that? I was unable to find a setting in the bios to switch primary gpus.

Link to post

I think you can move the primary gpu to slot 1, and the 5600xt to any other slot.

If I look at my system, the system is using slot 1 gpu to boot.

In any case attach the 5600xt to vfio.

Edited by ghost82
Link to post
2 minutes ago, ghost82 said:

I think you can move the primary gpu to slot 1, and the 5600xt to any other slot.

If I look at my system, the os is using slot 1 gpu to boot.

In any case attach the 5600xt to vfio.

OK thanks. I'll look into switching them around. Hopefully I can, the 5600XT is a large card. I won't be able to do that for a little while but once I do I'll update.

Link to post
On 1/6/2021 at 5:51 PM, jonathanm said:

 

On 1/7/2021 at 7:59 AM, ghost82 said:

I think you can move the primary gpu to slot 1, and the 5600xt to any other slot.

If I look at my system, the system is using slot 1 gpu to boot.

In any case attach the 5600xt to vfio.

Thanks for the help and recommendations! I swapped around the graphics cards, but was still having issues so I did a clean windows install and that seems to have fixed all of my issues. I really appreciate the help!

Link to post

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.