December 20, 20214 yr Thanks, this helped with my new rig (currently, we'll see if this becomes an issue later). Corsair products on an Aorus X570. 1 x Commander Pro connected to only USB2 serial port on board. 2 x Lighting Nodes connected to Commander Pro, via Seria Ports. 4 RGB fans to each lighting node (4 each). 1 x Corsair XD5 Pump and 1 x XC7 waterblock, daisy chained to 1st rgb port on Commander Pro. The VM Windows 10 wouldn't start because it found the 2 lightning nodes with the same vendor and product id on the USB 2 and kicked up an error. I changed the Commander Pro and the 2 lighting nodes to their bus and device ids as found in the System Devices tab. This made a heck of difference to me, so thanks.
December 27, 20214 yr Hi, Just an update on this. I found that I actually didn't need to do the above. The nodes and the Commander Pro were already available to the VM, all I had to do was select them with a tick in the Windows 10 VM, rather than trying to bind them to the vfio under the Tools/Devices page and then select them in the Windows 10 vm. After the USB controllers were passed through, it stated that connected USB devices would be hidden, being new to IOMMU binding, I didn't fully understand and was messing around with IOMMU groups to get them to work. Hope that helps somebody.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.