jimbobulator

I have this problem with the same microsoft keyboard, so I have opted to try passing the entire USB controller through, which I'm fine with. The VM boots up, but I still am losing the keyboard after a few seconds after it (the keyboard) powers up. I'd like to try the suggested fix below from Jude, but in 6.1 things are a bit different and the go file entry isnt apparently needed, so I'm not sure exactly how to do this. Here's the relevant section of my XML at the moment: <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pci.0,addr=1c.0,multifunction=on,port=2,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.1,bus=root.1,addr=00.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=00:1d.0,bus=root.1,addr=00.2'/> </qemu:commandline> Any thoughts? 00:1d.0 is the USB controller in question.

Just found that thread - will try that out when I get a chance. Thanks! Apologies for hijacking your thread claira...

Sadly I'm using a uATX board, and my sole PCIe slot has a video card for my htpc VM. I should just buy a different keyboard that actually works with device pass-through, but I'm stubborn. Honestly I just got frustrated and haven't had time to look at it since. Yes, I realize that each board will be different but I know there's at least a few people on here with the same MB.

I started this process, but the number of permutations between the 3 or 4 settings in my bios (each with 2-4 options) is ridiculous and I didn't have 4 hours to do trial and error. I found one combo that at least got it so unraid could see 2 independent controllers but I really would prefer seeing all 3. Some generic understanding of what these settings truly mean and how they affect the operation of the hardware would probably simplify the process, but I couldn't find this info online in the time I had available. Any help is appreciated. If I ever finish mapping all the combos out I'll post them for anyone with a similar motherboard.

I use the screengrab feature in OneNote. Windows+S, then drag a box around the part of the screen you want and it goes to the clipboard (or to a OneNote note if you set it up that way). Convenient if you already have OneNote and saves a step of cropping in paint.net.

You will use one docker container per application, this is due to the way docker is intended to work. It compartmentalizes, or containerizes your applications so they are isolated from each other. This makes it easier to update and manage them. It has nothing to do with threads, which you don't really need to worry about. As far as how docker containers takes advantage of your processor, unraid lets you decide which CPU cores and how many to make available to each application. Hope that helps. For performance questions regarding PS and your images, you might have better luck asking for feedback on a photography forum. You won't find as my computer experts but surely someone would have some performance feedback working with similar images on comparable hardware for a reference point.

Potentially obvious point but tripped me up the first time: when you browse to and select the various drivers as you are installing them, be sure to dig down to the amd64 folder for your version of windows. It doesn't dig through the folders recursively to find the driver.

My setup is overpowered for sure. That said, two things to keep in mind - in order to pass through a GPU you need VTd (or the AMD equivalent) technology in your processor, and you need a dedicated GPU because it's currently (maybe ever?) not possible to pass through integrated graphics to a VM. For intel processors, VTd support starts somewhere in the i5 range and somewhere in the Xeon e3 range, and I have no clue for AMD.

You will need a machine capable of passing hardware (GPU/Audio) through to your virtual machine. This means your motherboard and processor must both support IOMMU, called VTd in the intel world. You can find processors that support this via Intel's website and their filters. For the motherboard you'll need to consult manuals and/or search for examples proving it works. You'll want to search the forums and wiki for info on this, there's tons out there and no point rehashing it all here. Also read up on GPU passthrough using KVM, and pick an suitable known-working GPU based on this. I'm doing basically what you propose. I have the server and dockers running most of my applications, although I haven't finished setting up the HTPC VM yet. The GPU passthrough seems to work but I haven't completely tested everything. The VM more of a project than a requirement for me so it's not really a rush. Here's my build for a reference point: - Case: Fractal Design Node 304 - MB: Gigabyte H97N-WIFI (6 SATA ports) - PROC: Intel i5-4590 - RAM: 16GB patriot something or other - 3x 3TB Seagate drives (they were cheap and my storage needs are modest compared to most here) - 250GB Crucial SSD for docker appdata, VM vdisks, etc. - AMD 6540 video card passed through to the VM. Note that some Microsoft wireless keyboards don't play nicely with USB device passthrough on unraid at the moment and require passing a whole controller through. this is the reason I haven't completed my testing, because I'm having difficulty finding the right combination of bios settings to get the USB controllers to enumerate individually so they can be passed through.

Fair enough, I missed this when I read the thread backwards (facepalm). Based on my experience testing it seems that the WebUI does not get the same prioritization, and it's not clear if jonp's term unRAID OS covers the WebUI. If a docker is going crazy and using 100% of all cores, and I can't access the WebUI, I can't stop the docker. Well I can, but not without going to the command line, which it seems LT is trying to avoid users having to do. Not much more than an annoyance for me, but it's an opportunity for improvement. To clarify, my experience is that high CPU load from a docker container makes the WebUI extremely slow, bordering on unusable. I haven't seen it completely crash, but it gets slow enough that it's nearly unusable. I admit I have a low tolerance for this sort of UI behavior...

I have been planning to play with CPU pinning with my containers, because I'm running into problems where my CPU is pinned by a docker and I lose the ability to do anything else with the server. Clearly pinning CPUs intelligently will sort this out. That said, in the name of user friendliness, I think this setting this parameter needs to be improved in the Webui and ideally there should a way that unraid to maintain priority for NAS/Webui functionality, whether through default CPU pinning or process prioritization. In my opinion, add-on applications like dockers should be able to take over to the point where you can't interact with it anymore.