djrico20one1

I believe nvidia requires licensing, software and OS support for this to work, it's called Nvidia GRID.

https://github.com/P3R-CO/openrgb-container This one is now available in community apps it wraps openRGB mentioned above, just got it running on my server, So far I've got Mobo and AIO control, still working on getting the ram and graphics rgb control

Yes please!!! I'd really love this feature

When you click the vm icon you should see a menu, once you've clicked to start the vm, open that menu again and you should see an option to view logs.

Does the vm produce any logs while it is in that rotating state?

With your xml configured correctly you may not need the ACS override turned on. I have mine turned off and am passing a 2070 super to my vm. My IOMMU group shows this in system devices: IOMMU group 58: [10de:1e84] 4b:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] (rev a1) [10de:10f8] 4b:00.1 Audio device: NVIDIA Corporation TU104 HD Audio Controller (rev a1) [10de:1ad8] 4b:00.2 USB controller: NVIDIA Corporation TU104 USB 3.1 Host Controller (rev a1) [10de:1ad9] 4b:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU104 USB Type-C UCSI Controller (rev a1) And I've configured my xml as such: <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x4b' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/user/domains/vbios/Gigabyte.RTX2070Super.8192.190625_updated.rom'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x4b' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x4b' slot='0x00' function='0x2'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x4b' slot='0x00' function='0x3'/> </source> <alias name='hostdev3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/> </hostdev> You'll need to create these host dev sections for all 4 of the devices on your card, If you notice my slot values don't go in order, 0x06,0x08,0x09,0x0a Something else in my xml was already using 0x07, so just make sure when you populate those values you don't repeat one that already assigned. Based on your outputs above it looks like these are the 4 device you want to pass through: IOMMU group 30: [10de:1e84] 2d:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] (rev a1) IOMMU group 31: [10de:10f8] 2d:00.1 Audio device: NVIDIA Corporation TU104 HD Audio Controller (rev a1) IOMMU group 32: [10de:1ad8] 2d:00.2 USB controller: NVIDIA Corporation TU104 USB 3.1 Host Controller (rev a1) IOMMU group 33: [10de:1ad9] 2d:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU104 USB Type-C UCSI Controller (rev a1)

I know this is old, but I ran in to a similar problem today. I found a way to solve this so I figured I'd add it here for the next person. In my case I had been adding some usb devices manually, and thats what first caused the issue. but I see similar malformed xml in the configuration above. Try removing any usb configs with 2 address tags in them. then save and make your changes. <hostdev mode='subsystem' type='usb' managed='yes'> <source> <address bus='5' device='3'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> Basically any usb config that contains the <address> tag with a bus and device id shouldn't also have an address tag with type,bus, port. Usually you add the bus and device id when trying to pass through usb devices with matching vendor and product ids. But you should still remove the second address tag. I found it was easiest to remove all the offending usb configs. Save, and then reconfigure things correctly.

Did you ever find a solution to this?

What are some symptoms of missing QEMU Support? I googled it and it sounds like it would cause issues with running VM's but I haven't noticed any issues, granted I only have one MacOs VM running. I'm currently running unraid 6.8.2 on the following hardware: Gigabyte TRX40 AORUS XTREME Threadripper 3990x The mobo has dual 10gbps ethernet. I'm currently only using one of them ( haven't got around to configuring link aggregation yet ), but its recognizing both of them. I'm also using an nvidia GTX 960, ( Haven't decided on the new GPU yet ) and was able to get that handling hardware transcoding in a plex docker container via the Unraid Nvidia Plugin. All of this to say I haven't noticed any issues with sTRX40 and unraid. But to be fair this is my first unraid server, and I've only had it running for a couple weeks so maybe there may be things I just haven't run in to yet.