johnarvid

Ok, no that is not applicable for me. I use an "old" vm.

@bastl Do you mean first start of VM after host start? Or do you mean in the VM's lifetime?

Tested with 6.7rc5 but no improvement.

I probably have the same problem. Very slow boot when doing pass-through and much memory. First pinned cpu is working 100% Will try 6.7 soon, but this has been a problem since at least 2016 so I don't have any expectations. Same as Craig, let me know if any logs or other info is needed.

And just to confirm. (Since I did not find anything about vm-x) vm-x is Virtual Machine extensions? Also known as x86 virtualization? Or as unraid is reporting on System Profiler for the CPU, VME (Virtual mode extension)? Ref: https://en.wikipedia.org/wiki/VMX So if your cpu has VT-x (Intel) or AMD-V (AMD, doh) this would work? \John

I have followed these tutorials and tested different things that comments where mentioning. How to pass through an NVIDIA GPU as primary or only gpu in unRAID How to easily passthough a Nvidia GPU as primary without dumping your own vbios! in KVM unRAID The best way to install and setup a windows 10 vm as a daily driver or a Gaming VM All videos made by Spaceinvader One \JAK

Hence:

Hello, I wanted to share my story and ask for help regarding what to do next. Setup: Motherboard: ASrock x99x killer Gpu1: MSI gtx980 (Pci1) Gpu2: MSI gtx980 (Pci2) Gpu3: XFX 6950 (Pci3) Cpu: Intel I7 Ram: 64GB ddr4 HDD: 18TB What I want to do: Have three windows 10 virtual machines that has one gpu each, running at the same time. Atleast 4 usb port for each vm. (This has been solved in a way) (I have two Logitech G27 so me and a friend can play together, so the USB has to be passed through. This is working, can share if wanted, but the information is on the forum) What I have done/tested: Unraid uses the first GPU as it's head. I can successfully choose the Gpu2 and Gpu3 in Unraid GUI and start the VM. This works without a problem. But if I choose Gpu1 and start the VM, Unraid looses it's head, the screen goes black, all the CPU cores throttles and the VM starts. I can now log in via RDP but there is no screen output. When I log into the VM with RDP I get this error in device manager: Windows has stopped this device because it has reported problems. (Code 43) This led me to https://forums.lime-technology.com/topic/43785-solved-gpu-drivers-failing-in-windows-10-vm-code-43/ Tried to disable HyperV but it was the same problem. Tried the newest virtio drivers, same problem. Tried to install a new VM. If I choose Gpu1 and start the VM, there is no output to the screen, and the forums posts says that I should not use VNC at any time. (Tested with OVMF and SEABIOS) so I can't really proceed more on this step. But all information leads to using a VBIOS for the main GPU. Then if I use the VBIOS and add this to the xml, when I start the VM all the CPU cores throttles to almost 100% and stays this way for however long I wait. The VM does not start, so no RDP. I have tested with rom from my GPU, though I could only do a "cat rom" on Gpu2 and not on Gpu1. (input output error) I have tested with a rom from techpowerup after I removed the first part in a hex editor. I have also added vfio_iommu_type1.allow_unsafe_interrupts=1 with no luck. I'm sure I am doing something wrong, or missing something. It should not be that difficult to use Unraid!? Should it? \JAK