ncandy

It looks like tag 8.1.113-unraid was updated a day ago, according to Docker Hub. Perhaps this push was unintentional?

Sounds like you may have selected virbr0 instead of br0 as the Network Bridge for the VM. If you want your guest VMs to be on the same network as the host, change the bridge to br0. If you want the guest VM to be isolated from the host network, leave it on virbr0 and let the KVM/QEMU perform NAT.

On the docker settings page, toggle to Advanced View in the upper right. Do you have --runtime=nvidia set in Extra Parameters?

So it seems that nested virtualization was causing problems in my case. I reenabled WSL but left off Hyper-V and Windows Hypervisor Platform and everything is running normally. Interestingly, turning off Hyper-V in the Unraid VM settings did nothing to resolve the issue. I needed to disable virtualization features inside Windows itself.

I spent the weekend trying to diagnose the problems and I may have found something. These are the things I've tried with mixed results: Moved everything off my cache pool (2 Samsung EVO SSDs), repartitioned to 1MB alignment, moved everything back (my vdisks are on the cache pool) Updated virtio windows drivers to latest (0.1.190-1) Updated VM Machine to i440fx-5.1 (was i440fx-4.2) Changed VM network model to virtio-net (was virtio) Reduced RAM to 16384 MB (was 32768 MB) Moved Windows 10 VM vdisk to separate SSD in unassigned devices Changed VM to use /dev/urandom for RNG I have two Windows 10 VMs and only one is having problems. The last change I made this morning looks to have resolved the issue for me. In the Windows 10 VM that is slow, I went into Windows Features and disabled Hyper-V, Windows Hypervisor Platform and Windows Subsystem for Linux. After the required reboot, I no longer saw all cores hitting 100% with 50-80% from system processes. I also saw a dramatic change in the interrupt processing on the cores dedicated to that VM from Unraid's perspective. My next step is to turn Windows Subsystem for Linux back on since I do need it for this VM. Hope this info helps some of you experiencing slowness.

I might be experiencing the same symptoms. I upgraded from 6.8.3 to 6.9.0 and now to 6.9.1 and my Win10 VMs seem to be running much slower. I see long periods of high CPU utilization on a fresh boot with no applications started. Out of curiosity, do you store your VM disk images on an SSD cache pool? I just moved all of VM disk images off the cache and onto the array, and so far, it seems to help. Going to do some more testing, but I was planning to move everything off cache and repartition the SSDs to 1MB alignment anyways. Once aligned, I'll move the VM disk images back to cache to see if it helps.