August 30, 20223 yr unraid v 6.10.3 First, thank you all. I have been crawling these forums for weeks now. New to unraid. Hardware: AMD Rycen 5900X MSI X570 Edge Max WifiMB 64GB RAM Asus geforce RTX TUF gaming OC 12GB GPU EVGA 1300 G+ Supernova Today I installed Win 10 as a VM, closely following spaceinvader one's videos. When I got to the sections of setting up my nVidia GPU, this is where I hang, and I cannot find an answer to what I am experiencing. When the VM GPU is configured VNC, I have absolutely no issues. I can connect to the VM all day long. When I change the GPU to the nVidia GPU, set the vbios to the bios I downloaded following Spaceinvader one's vbios download script, and assigning the matching sound card on the GPU...i get no where. Cannot ping the VM. The network does not come up, at all. I confirmed this by running a ping -t from my laptop to the VM after switching back to VNC GPU, removing the sound card, etc. I can load the VM in VNC, but the continuous ping fails until I login to the VM, and only after I login is the ping successful. It looks like, to me, that when I change the GPU, the network fails. I have no idea what is happening and any help is appreciated. Diagnostics attached. IOMMU data: 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.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge IOMMU group 2: [1022:1483] 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge IOMMU group 3: [1022:1482] 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 4: [1022:1482] 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 5: [1022:1483] 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge IOMMU group 6: [1022:1482] 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 7: [1022:1482] 00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 8: [1022:1482] 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 9: [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 10: [1022:1482] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 11: [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 12: [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 13: [1022:1440] 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 0 [1022:1441] 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 1 [1022:1442] 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 2 [1022:1443] 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 3 [1022:1444] 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 4 [1022:1445] 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 5 [1022:1446] 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 6 [1022:1447] 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 7 IOMMU group 14: [126f:2263] 01:00.0 Non-Volatile memory controller: Silicon Motion, Inc. SM2263EN/SM2263XT SSD Controller (rev 03) [N:0:1:1] disk TEAM TM8FP6001T__1 /dev/nvme0n1 1.02TB IOMMU group 15: [1022:57ad] 20:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse Switch Upstream IOMMU group 16: [1022:57a3] 21:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 17: [1022:57a3] 21:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 18: [1022:57a3] 21:03.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 19: [1022:57a3] 21:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 20: [1022:57a3] 21:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 21: [1022:57a4] 21:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 22: [1022:57a4] 21:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 23: [1022:57a4] 21:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 24: [1987:5012] 22:00.0 Non-Volatile memory controller: Phison Electronics Corporation E12 NVMe Controller (rev 01) [N:1:1:1] disk PNY CS2130 2TB SSD__1 /dev/nvme1n1 2.00TB IOMMU group 25: [1987:5012] 23:00.0 Non-Volatile memory controller: Phison Electronics Corporation E12 NVMe Controller (rev 01) [N:2:1:1] disk PNY CS2130 2TB SSD__1 /dev/nvme2n1 2.00TB IOMMU group 26: [8086:105e] 25:00.0 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller D0/D1 (copper applications) (rev 06) IOMMU group 27: [8086:105e] 25:00.1 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller D0/D1 (copper applications) (rev 06) IOMMU group 28: [10ec:8125] 27:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05) IOMMU group 29: [8086:2725] 28:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a) IOMMU group 30: [1022:1485] 2a:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP IOMMU group 31: [1022:149c] 2a:00.1 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller Bus 001 Device 001 Port 1-0 ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002 Port 1-1 ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub Bus 001 Device 003 Port 1-2 ID 0db0:151f Micro Star International USB Audio Bus 001 Device 004 Port 1-1.1 ID 0781:5571 SanDisk Corp. Cruzer Fit Bus 001 Device 005 Port 1-4 ID 8087:0032 Intel Corp. AX210 Bluetooth Bus 001 Device 006 Port 1-1.3 ID 05af:8277 Jing-Mold Enterprise Co., Ltd USB Keyboard Bus 002 Device 001 Port 2-0 ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002 Port 2-1 ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub IOMMU group 32: [1022:149c] 2a:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller Bus 003 Device 001 Port 3-0 ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002 Port 3-5 ID 1462:7d53 Micro Star International MYSTIC LIGHT Bus 003 Device 003 Port 3-6 ID 05e3:0608 Genesys Logic, Inc. Hub Bus 004 Device 001 Port 4-0 ID 1d6b:0003 Linux Foundation 3.0 root hub IOMMU group 33: [1022:7901] 2b:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) IOMMU group 34: [1022:7901] 2c:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) [6:0:0:0] disk ATA WDC WD60EFAX-68J 0A83 /dev/sdc 6.00TB [7:0:0:0] disk ATA SPCC Solid State 6A0 /dev/sdd 2.04TB [10:0:0:0] disk ATA PNY CS900 500GB 0613 /dev/sde 500GB [11:0:0:0] disk ATA WDC WD60EFAX-68J 0A83 /dev/sdf 6.00TB IOMMU group 35: [10de:2504] 2d:00.0 VGA compatible controller: NVIDIA Corporation GA106 [GeForce RTX 3060 Lite Hash Rate] (rev a1) IOMMU group 36: [10de:228e] 2d:00.1 Audio device: NVIDIA Corporation Device 228e (rev a1) IOMMU group 37: [1022:148a] 2e:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function IOMMU group 38: [1022:1485] 2f:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP IOMMU group 39: [1022:1486] 2f:00.1 Encryption controller: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP IOMMU group 40: [1022:149c] 2f:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller Bus 005 Device 001 Port 5-0 ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001 Port 6-0 ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 006 Device 002 Port 6-1 ID 154b:00ed PNY USB 3.0 FD IOMMU group 41: [1022:1487] 2f:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller CPU Thread Pairings Pair 1: cpu 0 / cpu 12 Pair 2: cpu 1 / cpu 13 Pair 3: cpu 2 / cpu 14 Pair 4: cpu 3 / cpu 15 Pair 5: cpu 4 / cpu 16 Pair 6: cpu 5 / cpu 17 Pair 7: cpu 6 / cpu 18 Pair 8: cpu 7 / cpu 19 Pair 9: cpu 8 / cpu 20 Pair 10: cpu 9 / cpu 21 Pair 11: cpu 10 / cpu 22 Pair 12: cpu 11 / cpu 23 USB Devices Bus 001 Device 001 Port 1-0 ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002 Port 1-1 ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub Bus 001 Device 003 Port 1-2 ID 0db0:151f Micro Star International USB Audio Bus 001 Device 004 Port 1-1.1 ID 0781:5571 SanDisk Corp. Cruzer Fit Bus 001 Device 005 Port 1-4 ID 8087:0032 Intel Corp. AX210 Bluetooth Bus 001 Device 006 Port 1-1.3 ID 05af:8277 Jing-Mold Enterprise Co., Ltd USB Keyboard Bus 002 Device 001 Port 2-0 ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002 Port 2-1 ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub Bus 003 Device 001 Port 3-0 ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002 Port 3-5 ID 1462:7d53 Micro Star International MYSTIC LIGHT Bus 003 Device 003 Port 3-6 ID 05e3:0608 Genesys Logic, Inc. Hub Bus 004 Device 001 Port 4-0 ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001 Port 5-0 ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001 Port 6-0 ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 006 Device 002 Port 6-1 ID 154b:00ed PNY USB 3.0 FD SCSI Devices [0:0:0:0] disk PNY USB 3.0 FD PMAP /dev/sda 61.9GB [1:0:0:0] disk SanDisk' Cruzer Fit 1.00 /dev/sdb 16.0GB [6:0:0:0] disk ATA WDC WD60EFAX-68J 0A83 /dev/sdc 6.00TB [7:0:0:0] disk ATA SPCC Solid State 6A0 /dev/sdd 2.04TB [10:0:0:0] disk ATA PNY CS900 500GB 0613 /dev/sde 500GB [11:0:0:0] disk ATA WDC WD60EFAX-68J 0A83 /dev/sdf 6.00TB [N:0:1:1] disk TEAM TM8FP6001T__1 /dev/nvme0n1 1.02TB [N:1:1:1] disk PNY CS2130 2TB SSD__1 /dev/nvme1n1 2.00TB [N:2:1:1] disk PNY CS2130 2TB SSD__1 /dev/nvme2n1 2.00TB tower-diagnostics-20220830-1807.zip
September 2, 20223 yr Author So I walked away from it for a few days hoping a solution would come to me. Not so much. Every time I attach the GPU to the VM the network drops out. Period. I have statically assigned the IP in the VM. I am using PiHole as an DHCP server and reserved the IP in PiHole. My UDM Pro see the VM on the network with the correctly assigned PiHole IP address. The closest I got was when I added the VNC GPU as the primary and the Asus card as secondary, I can get to the windows login screen and login - right before the VM crashes and I get "Select your keyboard layout" and then "troubleshoot your pc". I start the ping to test the network just before starting the VM and this is what it looks like with VNC as the primary GPU and Asus GPU as the secondary: The VM shows this log output of cat /proc/iomem Its really a bummer unraid doesnt have a web browser based method to access the VM when the network isnt working to troubleshoot, similar to vsphere. It would be nice to know if the VM is somehow getting a different IP address when it starts up or look at the windows logs from the inside. Im going to remove the IP reservations in pihole and clear the static address in the vm, see if something different shows up in my network other than the expected address. Im truly lost at this point, and searching around isnt really offering me any real clue as to what is going on.
September 2, 20223 yr Author I got it. I was missing one configuration. My system only has the one gpu. I forgot to add the configuration that forced unraid to boot without gpu. Once I put this setting in, everything worked. I understand why this setting is required. What I don't understand is why not having this setting was causing the vm on the network to crash.
September 3, 20223 yr Because you didn't have loaded windows. Windows doesn't boot without gpu.... The thing is that most of this videos are not relevant anymore. A lot of things change. The thing you have to do for the gpu to not been used by unraid and to be bind to vfio driver is. Unraid GUI>TOOLS>System Devices>mark the check box of the device>click on bind to vfio>reboot.
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.