Ancalagon

@celborn sorry for the late reply. The bottom 2 of those 4 devices are correct. The top 2 are not though. You need the other 2 below that are on 04:00.2 and 04.00.3. This is mine:

I've been attempting to do the same for the 7950x iGPU. I've been able to pass through the Radeon RX 6800 XT and RX 7900 XT GPUs, but I haven't had any luck or found any specific info on the Ryzen 7000 iGPUs. I've added the GPU and audio device to a Windows 11 VM and adjusted the XML so they're on the same bus and slot as a multfunction device. If I remote into the VM, I can see the GPU with a code 43 error. I was able to workaround this same error by using a vBIOS rom for the 7900 XT. I tried exporting the 7950x iGPU vBIOS with GPU-Z, but just got an error message: "BIOS reading not supported on this device". I'm not sure if this is an issue with the iGPU or GPU-Z. I also couldn't find a vBIOS online anywhere. My other thought was maybe besides the VGA and audio devices, it may require the other three devices on the same bus and slot: Encryption controller: Advanced Micro Devices, Inc. [AMD] VanGogh PSP/CCP USB controller: Advanced Micro Devices, Inc. [AMD] Device 15b6 USB controller: Advanced Micro Devices, Inc. [AMD] Device 15b7 I tried adding the encryption controller, but it just shows up as not having a driver (and it won't let me install the AMD chipset drivers in a VM). I didn't try the USB controllers as well. The second controller actually has my UnRAID flash drive, so I'd have to find another USB port on an unused controller to be able to add it.

I find that this app always requires a "force update" in order to update. Is this because the Docker repository seems to delete older images and only keeps a single latest? Is there any way to avoid this?

The size of their cards is bonkers now too. For one of my machines, Nvidia cards don't come close to fitting in the case. I also prefer AMD to be able to run macOS VMs (hopefully eventually supported for RX 7000 series).

Come to think of it, I don't think I have. I have seen the progress circle with the Windows 11 logo. That may have been after booting in CSM mode. I think it usually goes straight to the Windows login screen like you said though. I've been using Q35-7.1 myself.

Great to hear. After I got this working, I was messing around with it more to see if there were other ways I could get it working without needing the vbios, but never found one. But afterwards reverting the changes, it wasn't consistent getting it to work again, even after using the same steps (booting into CSM mode first, etc.). But once it works, it seems to continue working, restarting the VM multiple times and never had it stop working. When it wasn't working (always code 43), I found booting the VM with only the GPU passed through without other passed through hardware worked. Whether that was a coincidence or not, I can't say. It's definitely more finicky than the RX 6800 XT was.

I'm using the original vbios dump, no edits. Yes, I am binding all 4 devices to vfio. After adding them to the VM, I'm manually editing the XML to put them on the same bus and slot as a multifunction device. Here's the GPU portion of my XML: <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0c' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/user/domains/GPU ROM/AMD.RX7900XT.022.001.002.008.000001.rom'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0c' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x1'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0c' slot='0x00' function='0x2'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x2'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0c' slot='0x00' function='0x3'/> </source> <alias name='hostdev3'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x3'/> </hostdev> Have you been able to boot the VM after booting the host in legacy CSM mode?

I used GPU-Z.

This is an excellent suggestion. There's a similar request here.

GPU resizable BAR support is coming in Linux kernel 6.1. It'd be great to support this natively in Unraid, somehow in the VM GUI or a setting or at least a documented script or how-to.

I got this working! First, I was able to successfully pass through the GPU after switching to legacy CSM boot. I was then able to save my vbios rom. Then after adding the vbios rom to the VM XML and switching back to EFI boot, the GPU passthrough works! I can also confirm the GPU is properly reset when rebooting the VM as well.

Thanks. I just tried this and got the same code 43 behavior.

Has anyone tried passing an AMD Navi 31 (Radeon RX 7900 XT or XTX) GPU through to a VM yet? I just got the RX 7900 XT and have not had luck passing to a Windows 11 VM. I'm upgrading from an RX 6800 XT, which I had working previously. These are steps I've taken: Bind 0d:00.0, 0d:00.1, 0d:00.2, and 0d:00.3 IOMMU groups to VFIO at boot append initrd=/bzroot video=efifb:off in Syslinux Configuration <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0' multifunction='on'/> in VM XML Change other three GPU devices to same bus and slot with own function, i.e. <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x1'/> After Unraid reboot, on first VM boot, nothing displays on attached monitor. Remoted into the VM with RDP, the GPU shows code 43 error in device manager. After rebooting the VM, the GPU doesn't show up in device manager at all.

Another solution, you can set the network model to vmxnet3, which has driver support included in Windows 11. Once everything is set up, and virtio drivers installed, you can switch the network model back to virtio.

Not to the same extent, in that the usage should be roughly equal between all the drives in a btrfs cache pool and if it's a RAID1 mirror, the total pool size and usage will be half of the total individual drives' usage. But there's still the concept of individual drive usage vs total pool usage, just not as relevant to see though. Is this bug expected to be fixed in the next Unraid release? This is true, in that the individual drive free space will converge to 0 at the same speed as the total free space converges to 0. The values will get closer, but never truly be accurate until the pool is completely full.

It seems like this UI would be more intuitive if it mirrored the arrays UI, where next to each drive it showed the size, used, and free space on each drive and at the bottom, the total size, used, and free space.

I have 3x4TB NVMe disks in a btrfs cache pool. In the Unraid GUI, it shows the size to be 6TB, which is what I expect. It shows the used space as 712GB (the amount of data I copied to the cache pool). But the free space shows as only 3.53TB, which is not what I'd expect. This seems like it might be the amount of free space on a single drive in the pool, but I'd expect it to show the total free space as ~5.29TB. Indeed, 3.53 x 3 / 2 ~= 5.29.

I'm building a second computer and was considering running Unraid as the OS for flexibility installing VMs and as a backup storage array. But it will be located in a room that does not have wired Ethernet. Its primary purpose requires it to be in this location. Without Wi-Fi support, I won't be able to use Unraid and will have to install another OS with Wi-Fi support.

Would it be possible to add fswatch? https://slackbuilds.org/repository/15.0/system/fswatch/ The latest release is 1.17.1. https://github.com/emcrisostomo/fswatch/releases

It looks like the NVRAM is not being cleared, as I can still see the legacy NVRAM variable with the old OpenCore version: 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version = REL-064-2020-11-13. I've tried with the Reset NVRAM option in the boot menu as well as sudo nvram -c from the terminal. Apparently neither worked to delete that variable. I finally got it to delete explicitly with nvram -d 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version from the terminal. Rebooting it now shows the correct OpenCore version in OpenCore Configurator and Hackintool.

I installed a macOS Big Sur VM using the latest macinabox. After installing OpenCore Configurator 2.39.0.0, it warned about the old version of OpenCore installed (0.6.4) and only supporting the latest 0.6.9 version. I followed the documentation for updating OpenCore by copying over all the files from the 0.6.9 package to the EFI partition, overwriting existing files and keeping all the files in the existing EFI that aren't in the 0.6.9 package. But when I reboot, it still says OpenCore 0.6.4 is booted. I found there was a bug updating to 0.6.7 that required clearing the nvram. But even after clearing the nvram, it still says 0.6.4 is booted. It does say the correct version on the boot menu though: (REL-069-2021-05-03). Are there any additional steps required to update OpenCore for the macinabox VM?

I have a similar setup with ASUS ROG Crosshair VIII Dark Hero, Ryzen 9 5950x, and AMD Radeon RX 6800 XT (reference), running Unraid 6.9.2 with a Windows 10 VM. I found that adding "video=efifb:off" was required in the Syslinux configurations: append initrd=/bzroot video=efifb:off Binding the 4 IOMMU groups to VFIO at boot wasn't enough apparently. I'm using Q35-5.1 and also have Smart Access Memory enabled in the BIOS, although it's set to AUTO (there is only DISABLED and AUTO). I found I had to reinstall the Radeon driver after getting it to boot. I also found that it failed to work with the GPU as the secondary graphics, with VNC graphics as primary. I had to remove the VNC graphics.