Issue with GPU with my 1080ti

[Numble01]

Operating system

Unraid 7.1.0-rc.4

Description

So I used the guide in GPU thread and got working , using the PCI Devices and IOMMU Groups in unraid. So it ran, worked fine. Updated/added Nvidia drivers and had to reboot and then got the below error message. Restarted the container, same result. Rebooted my the server and then it works but its very laggy and the mouse hardly moves.

Docker compose

N/A

Docker log

❯ ERROR: Timeout while waiting for QEMU to boot the machine!
❯ ERROR: Timeout while waiting for QEMU to boot the machine!

dnsmasq: failed to create inotify: Too many open files
❯ ERROR: Failed to start dnsmasq, reason: 0
❯ Warning: an error occured, falling back to user-mode networking!
❯ ERROR: Timeout while waiting for QEMU to boot the machine!
❯ Starting Windows for Docker v4.34...
❯ For support visit https://github.com/dockur/windows
❯ CPU: Intel Core i5 14500 | RAM: 39/63 GB | DISK: 887 GB (xfs) | KERNEL: 6.12.24-Unraid...

❯ Booting Windows using QEMU v9.2.92...
qemu-system-x86_64: vfio: Cannot reset device 0000:01:00.1, no available reset mechanism.
qemu-system-x86_64: vfio: Cannot reset device 0000:01:00.0, no available reset mechanism.
qemu-system-x86_64: vfio: Cannot reset device 0000:01:00.1, no available reset mechanism.
qemu-system-x86_64: vfio: Cannot reset device 0000:01:00.0, no available reset mechanism.
qemu-system-x86_64: warning: vfio_container_dma_map(0x55daaa437400, 0x380000000000, 0x10000000, 0x1501e0000000) = -22 (Invalid argument)
0000:01:00.0: PCI peer-to-peer transactions on BARs are not supported.
qemu-system-x86_64: terminating on signal 15 from pid 283 ()
❯ Shutdown completed!
❯ Starting Windows for Docker v4.34...
❯ For support visit https://github.com/dockur/windows
❯ CPU: Intel Core i5 14500 | RAM: 54/63 GB | DISK: 887 GB (xfs) | KERNEL: 6.12.24-Unraid...

❯ Booting Windows using QEMU v9.2.92...
qemu-system-x86_64: vfio: Cannot reset device 0000:01:00.1, no available reset mechanism.
qemu-system-x86_64: vfio: Cannot reset device 0000:01:00.0, no available reset mechanism.
qemu-system-x86_64: vfio: Cannot reset device 0000:01:00.1, no available reset mechanism.
qemu-system-x86_64: vfio: Cannot reset device 0000:01:00.0, no available reset mechanism.
qemu-system-x86_64: warning: vfio_container_dma_map(0x55a167787400, 0x380000000000, 0x10000000, 0x153d30000000) = -22 (Invalid argument)
0000:01:00.0: PCI peer-to-peer transactions on BARs are not supported.
qemu-system-x86_64: terminating on signal 15 from pid 284 ()
❯ Shutdown completed!
❯ Starting Windows for Docker v4.34...
❯ For support visit https://github.com/dockur/windows
❯ CPU: Intel Core i5 14500 | RAM: 43/63 GB | DISK: 887 GB (xfs) | KERNEL: 6.12.24-Unraid...

❯ Notice: port mapping will not work without "USER_PORTS" now.
❯ Booting Windows using QEMU v9.2.92...
qemu-system-x86_64: vfio: Cannot reset device 0000:01:00.1, no available reset mechanism.
qemu-system-x86_64: vfio: Cannot reset device 0000:01:00.0, no available reset mechanism.
qemu-system-x86_64: vfio: Cannot reset device 0000:01:00.1, no available reset mechanism.
qemu-system-x86_64: vfio: Cannot reset device 0000:01:00.0, no available reset mechanism.
qemu-system-x86_64: warning: vfio_container_dma_map(0x55fbf1014600, 0x380000000000, 0x10000000, 0x145b50000000) = -22 (Invalid argument)
0000:01:00.0: PCI peer-to-peer transactions on BARs are not supported.
qemu-system-x86_64: terminating on signal 15 from pid 286 ()
❯ Shutdown completed!

** Press ANY KEY to close this window **

Screenshots (optional)

[kikislater]

Install proxmox, this is the same thing with better support

[Numble01]

Guess what ive been doing this week:P Trying figure out the fun of proxmox!