Starli0n Posted August 25, 2020 Share Posted August 25, 2020 (edited) Hi, I have a Gigabyte X570 AORUS MASTER with 3x NVME slots on board: NVME 0: Used for a bare metal install of Win10 NVME 1: Used for a cache drive for Unraid NVME 2: Not used for now I successfully installed Win10 as a bare metal and configured correctly the cache drive for Unraid. But when I tried to passthrough the NVME 0 to Unraid to create a Win10 VM from the bare metal installation, the cache drive disappears from Unraid. I suspect that there is only one controller for the 3 NVME. And that controller can only be affected either to Unraid or either to pass through a VM. Is there a way to allocate the NVME 0 for the VM and the NVME 1 for the cache of Unraid ? --- Just in case, here is my configuration. Before PCIe ACS override was activated: IOMMU group 0: [1022:1482] 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1483] 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1987:5016] 01:00.0 Non-Volatile memory controller: Phison Electronics Corporation E16 PCIe4 NVMe Controller (rev 01) [1022:57ad] 02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse Switch Upstream [1022:57a3] 03:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge [1022:57a3] 03:03.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge [1022:57a3] 03:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge [1022:57a3] 03:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge [1022:57a4] 03:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge [1022:57a4] 03:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge [1022:57a4] 03:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge [1987:5016] 04:00.0 Non-Volatile memory controller: Phison Electronics Corporation E16 PCIe4 NVMe Controller (rev 01) [8086:2723] 05:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a) [8086:1539] 06:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03) [10ec:8125] 07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 01) [1022:1485] 08:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:149c] 08:00.1 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c] 08:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:7901] 09:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) [1022:7901] 0a:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) IOMMU group 1: [1022:1482] 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 2: [1022:1482] 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1483] 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [10de:1e84] 0b:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] (rev a1) [10de:10f8] 0b:00.1 Audio device: NVIDIA Corporation TU104 HD Audio Controller (rev a1) [10de:1ad8] 0b:00.2 USB controller: NVIDIA Corporation TU104 USB 3.1 Host Controller (rev a1) [10de:1ad9] 0b:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU104 USB Type-C UCSI Controller (rev a1) IOMMU group 3: [1022:1482] 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 4: [1022:1482] 00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 5: [1022:1482] 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 6: [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 7: [1022:1482] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 8: [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 9: [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 10: [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 11: [1022:148a] 0c:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function IOMMU group 12: [1022:1485] 0d:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP IOMMU group 13: [1022:1486] 0d:00.1 Encryption controller: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP IOMMU group 14: [1022:149c] 0d:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller IOMMU group 15: [1022:1487] 0d:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller Settings available for the VM: USB Devices: - Logitech Unifying Receiver (046d:c52b) - Integrated Technology Express ITE Device(8595) (048d:8297) - Intel Corp. (8087:0029) Other PCI Devices: - None available After PCIe ACS override is activated: 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 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 14: [1987:5016] 01:00.0 Non-Volatile memory controller: Phison Electronics Corporation E16 PCIe4 NVMe Controller (rev 01) IOMMU group 15: [1022:57ad] 02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse Switch Upstream IOMMU group 16: [1022:57a3] 03:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 17: [1022:57a3] 03:03.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 18: [1022:57a3] 03:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 19: [1022:57a3] 03:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 20: [1022:57a4] 03:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 21: [1022:57a4] 03:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 22: [1022:57a4] 03:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 23: [1987:5016] 04:00.0 Non-Volatile memory controller: Phison Electronics Corporation E16 PCIe4 NVMe Controller (rev 01) IOMMU group 24: [8086:2723] 05:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a) IOMMU group 25: [8086:1539] 06:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03) IOMMU group 26: [10ec:8125] 07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 01) IOMMU group 27: [1022:1485] 08:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP IOMMU group 28: [1022:149c] 08:00.1 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller IOMMU group 29: [1022:149c] 08:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller IOMMU group 30: [1022:7901] 09:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) IOMMU group 31: [1022:7901] 0a:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) IOMMU group 32: [10de:1e84] 0b:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] (rev a1) IOMMU group 33: [10de:10f8] 0b:00.1 Audio device: NVIDIA Corporation TU104 HD Audio Controller (rev a1) IOMMU group 34: [10de:1ad8] 0b:00.2 USB controller: NVIDIA Corporation TU104 USB 3.1 Host Controller (rev a1) IOMMU group 35: [10de:1ad9] 0b:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU104 USB Type-C UCSI Controller (rev a1) IOMMU group 36: [1022:148a] 0c:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function IOMMU group 37: [1022:1485] 0d:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP IOMMU group 38: [1022:1486] 0d:00.1 Encryption controller: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP IOMMU group 39: [1022:149c] 0d:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller IOMMU group 40: [1022:1487] 0d:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller As you can see the NVME have both the same ID but in different group: ... IOMMU group 14: [1987:5016] 01:00.0 Non-Volatile memory controller: Phison Electronics Corporation E16 PCIe4 NVMe Controller (rev 01) ... IOMMU group 23: [1987:5016] 04:00.0 Non-Volatile memory controller: Phison Electronics Corporation E16 PCIe4 NVMe Controller (rev 01) ... So I updated the boot sequence: kernel /bzimage append pcie_acs_override=downstream,multifunction initrd=/bzroot vfio-pci.ids=1987:5016 Settings available for the VM: USB Devices: - Logitech Unifying Receiver (046d:c52b) - Integrated Technology Express ITE Device(8595) (048d:8297) - Intel Corp. (8087:0029) Other PCI Devices: - Phison Electronics E16 PCIe4 NVMe Controller | Non-Volatile memory controller (01:00.0) - Phison Electronics E16 PCIe4 NVMe Controller | Non-Volatile memory controller (04:00.0) I can see both NVME drives but the cache drive is not longer available for Unraid 😕 Do you know a workaround for this ? --- Solution: Bios: Enable virtualization SVM mode Explicitly enable AMD IOMMU option (Default: Auto is not enough) Enable CSM Support Storage Boot Option Control: Legacy Only (ie: Boot Unraid in legacy mode) Other PCI Device ROM Priority: UEFI Only (ie: Boot Windows Bare Metal in UEFI mode) Unraid Boot (Main > Flash): Unraid OS kernel /bzimage append pcie_acs_override=downstream,multifunction initrd=/bzroot Server boot mode: Legacy Permit UEFI boot mode: disable Settings > VM Manager (Advanced View): PCIe ACS override: Both Settings > VFIO-PCI Config (plugin): Enable: Group 14 01:00.01987:5016Non-Volatile memory controller: Phison Electronics Corporation E16 PCIe4 NVMe Controller (rev 01) Dump Graphics ROM Bios VMS > Windows 10 BareMetal > Edit Bios: OVMF Hyper-V: No VirtIO Drivers ISO: /mnt/user/isos/virtio-win-0.1.173-2.iso Graphics Card: NVIDIA GeForce RTX 2070 SUPER (0b:00.0) Graphics ROM Bios: /mnt/user/domains/hardware/GPU/Gigabyte.RTX2070Super.90.04.95.00.86.gpuz.noheader.rom Sound Card: NVIDIA TU104 HD Audio Controller (0b:00.1) Other PCI Devices: Phison Electronics E16 PCIe4 NVMe Controller | Non-Volatile memory controller (01:00.0) XML View <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0' multifunction='on'/> (...) <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x1'/> --- Sources: SpaceInvader One How to dual boot baremetal windows and unRAID then boot the same windows as a vm A little about Passthrough, PCIe, IOMMU Groups and breaking them up How to easily passthough a Nvidia GPU as primary without dumping your own vbios! in KVM unRAID Advanced GPU passthrough techniques on Unraid https://www.techpowerup.com/gpuz https://mh-nexus.de/en/hxd Edited October 29, 2020 by Starli0n Solved 1 Quote Link to comment
testdasi Posted August 25, 2020 Share Posted August 25, 2020 Remote your vfio-pci.ids line, install VFIO-PCI config plugin (look in the app store), use that plugin (Settings -> VFIO-PCI CFG) to bind only the device that you need. That's the only way to do it when you have multiple of the same ID. FYI, in 6.9.0-beta25, the plugin is built into Unraid and the binding can be done in Tools -> System Devices so the vfio-pci.ids method probably isn't required anymore. Quote Link to comment
Starli0n Posted August 26, 2020 Author Share Posted August 26, 2020 (edited) Thank you very much for this plugin 👍 At first, I deactivated "PCIe ACS override" feature and remove the line from the "vfio-pci.ids=1987:5016". But after I pass through the NVME 0, I had the following error at Unraid boot: ... /etc/rc.d/rc.inet1: line 241: /proc/sys/net/ipv6/conf/eth0/disable_ipv6: No such file or directory ... IPv4 address: not set IPv6 address: not set ... So I had no more network and even after rebooting in safe mode without plugins did not work. I had to reboot in Gui mode to deactivate the passthrough of the drive and be back to normal. So I figured out that I need to reactivate the "PCIe ACS override" feature. By the way, do you know the difference between "Downstream" and "Multi-function" ? As I did not know, I activated both. Then I could start the Win10 VM with the NVME 0 passthrough as it has its own IOMMU group 🎉 My graphic card seems to work well as I did not need to install the drivers. However, I had no internet inside the VM. I figured out that I needed to install the VirtIO drivers thanks to Default "Windows VirtIO driver ISO" feature. But after installing, the VirtIO drivers, I have now a BLACK SCREEN after rebooting the VM 😩 I do not know why because the pass through of the graphic card was working well just before. Please note that I installed the missing drivers only for the network card from the Device Manager panel of Windows by clicking on browsing on the ISO. I have no graphic card on board. Edited August 26, 2020 by Starli0n Quote Link to comment
testdasi Posted August 26, 2020 Share Posted August 26, 2020 VFIO-PCI binding will automatically try to bind everything in the same IOMMU group as the device you tick (because it would be pointless to bind part of an IOMMU group). Your NIC is in the same group as your NVMe so ACS override is the only way. By the way, there's a VFIO-PCI.cfg file in the config folder of your flash - deleting that file will undo all the binding. Graphic card without drivers is a myth. Always install Nvidia driver to verify your install, including rebooting your VM to verify reset issue. You might want to watch SpaceInvader One tutorials on Youtube which probably will help with things. Quote Link to comment
Starli0n Posted August 26, 2020 Author Share Posted August 26, 2020 Thank you for the precision regarding VFIO-PCI settings. Even though, I did not get the difference between "Downstream" and "Multi-function". Regarding the drivers, sorry for being unclear. I installed all the necessary drivers including motherboard, graphic cards etc... during the install of the bare metal Windows. That's why I just needed to deal with the network because as far as I understood it is the only part which is emulated. When I successfully booted the VM for the first time, I had the same resolution than when booting on the bare metal. I will have a look on the tutorial you mentioned, I already watched some but I guess I miss this one. What bother me is that the display was working just before installing the VirtIO drivers... Quote Link to comment
Starli0n Posted September 2, 2020 Author Share Posted September 2, 2020 (edited) Indeed, watching others tutorials from SpaceInvader One helped me. I needed to dump the bios from my graphic card using the tool GPU-Z (HOWTO😞 https://www.techpowerup.com/gpuz As I have an Nvidia card, I needed to remove the header using the tool HxD (HOWTO😞 https://mh-nexus.de/en/hxd Then put the dump in a path like the following and update the VM template accordingly /mnt/user/domains/hardware/GPU/Gigabyte.RTX2070Super.90.04.95.00.86.gpuz.noheader.rom Finally, I needed to passthrough both GPU and sound of the graphic card using the multifunction method while editing the template with the xml view (HOWTO). <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0b' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/domains/hardware/GPU/Gigabyte.RTX2070Super.90.04.95.00.86.gpuz.noheader.rom'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0' multifunction='on'/> <!-- Update here --> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0b' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x1'/> <!-- And here --> </hostdev> I made a huge step as I could boot on my baremetal Windows VM. However my graphic card seems to still not be recognized even after updating to the last Nvidia drivers. Do the Gigabyte RTX 2070 Super is compatible with Unraid ? Sources: How to easily passthough a Nvidia GPU as primary without dumping your own vbios! in KVM unRAID Advanced GPU passthrough techniques on Unraid Edited September 2, 2020 by Starli0n Quote Link to comment
Starli0n Posted September 11, 2020 Author Share Posted September 11, 2020 I needed to boot Unraid in legacy mode while booting Windows Bare Metal in UEFI. Therefore, I needed to change some settings in my Bios: Enable CSM Support Storage Boot Option Control: Legacy Only (ie: Boot Unraid in legacy mode) Other PCI Device ROM Priority: UEFI Only (ie: Boot Windows Bare Metal in UEFI mode) So the Windows seems to boot pretty well from Unraid. However, I have an other issue in the Unraid Gui which seems to be down. I do not know the exact reason. Maybe I allocated to many CPUs for the VM. Luckily, I can still connect with ssh and perform a graceful shutdown. I am almost there... Quote Link to comment
Starli0n Posted October 29, 2020 Author Share Posted October 29, 2020 Unraid was working while accessing it by its IP address. Therefore, I realize that, I had a conflict of hostname between Unraid and the VM. I changed the name of the VM inside windows and everything went fine. I could access Unraid with the hostname. Problem solved 🎉 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.