Baltostar

Changed Status to Open Changed Priority to Annoyance

The script I wrote was to detect and attach the vive components to the PC because of one key issue. I discovered that editing the xml and specifying the IDs will work but only as you don't change anything on your pc configuration. If you unplug any of the vive USBs and plug them back in, you will loose connection to your vive. The script is to attach the vive to the running VM without reboot. If you do reboot your VM, it will give a device error because the USB Vive is registered as a different ID when you plug it back in. Do you have time to test unplugging the Vive, rebooting the VM and confirming that it will give you an XML error when you attempt to start? Then using the script to attach the vive back to your running VM. If everything works for you at that point, I'll set up a new windows 10 to confirm the process. After that I'll update the main post and reference your contribution. Thank you.

Thank you

I'm not sure if this is a bug or a feature request. When running with 'Ransomware Protection' configured to create file shares and files. That plugin creates files with same name but different camel casing. Duplicate files with different casing is something that 'Fix Common Problems' is designed to find. I want to exclude Fix Common Problems from searching my 'Ransomware Protection' created folders that have these incorrect casing issues are reporting on. I added the folders to the 'Permission Test/Fix Excluded On' section however they are still scanned for the same files with different capitalization. This means that the plugin will continue to report errors on these folders so I will always have to review results instead of relying on a pass fail message. If 'Permission Test/Fix Excluded On' being the only excluding option also applies to the capitalization search, then this is a bug because it isn't excluding it from the search. However if that that isn't the case, then the feature request is for adding an excluded section for the Capitalization scan.

The best way to run the vive on a VM is by passing the USB controller. Some controllers still have issues. Even without running on a VM, there can be issues. I pass a USB 3.1 controller on my new ASUS x99 board and run my vive off that. I started this post when I didn't have such options with my older x99 ASRock board. If you pass a USB 2/3 controller though and you still have issues, then consider buying one of the PCIe USB 3.1 cards and passing that though. https://www.reddit.com/r/Vive/comments/4l0c68/psa_getting_a_pcie_usb_3_card_solved_all_my_vive/ To be honest with you. It took me 5 months just to get my setup working due to the motherboard dropping a GPU and crashing my machine at random intervals, that once I had it working, i set up the Vive and haven't touched the occulus yet. It is still in its plastic wrapping. I've been waiting for the touch sensors on the occulus. The vive was just on sale, during Black Friday. If you do get the vive, don't get two if you will be using them in the same room because the lighthouses will interfere with each other.

My command: mapusb viveTempFolder '0bb4 0d8c 0424 28de' '1 GPU Middle WIN 10' Based on your post. These are the Vive devices: [b]Devices that normal passing the USB works fine because the ids are different.[/b] Bus 001 Device 002: ID 0bb4:2744 HTC (High Tech Computer Corp.) #Identified by row containing: 0bb4 Bus 001 Device 004: ID 0bb4:2134 HTC (High Tech Computer Corp.) #Identified by row containing: 0bb4 Bus 001 Device 005: ID 0bb4:0306 HTC (High Tech Computer Corp.) #Identified by row containing: 0bb4 Bus 001 Device 007: ID 0424:274d Standard Microsystems Corp. #Identified by row containing: 0424 Bus 001 Device 009: ID 0d8c:0012 C-Media Electronics, Inc. #Identified by row containing: 0d8c [b]This is the first source of frustration with passing vive to VM. They reused the same USB component here twice[/b] Bus 001 Device 008: ID 0bb4:2c87 HTC (High Tech Computer Corp.) #Identified by row containing: 0bb4 Bus 001 Device 010: ID 0bb4:2c87 HTC (High Tech Computer Corp.) #Identified by row containing: 0bb4 Issue here is same IDs and no name so it doesn't show up on GUIs Bus 001 Device 011: ID 28de:2101 #Identified by row containing: 28de Bus 001 Device 012: ID 28de:2101 #Identified by row containing: 28de No name so it doesn't show up on GUI. Bus 001 Device 006: ID 28de:2000 #Identified by row containing: 28de If your using my script. the command would be #I had the script as a function for testing, so I use source to make that function available. The viveTempFolder can be left like that. it will create a folder with that name to store xml configs for debugging reasons. The only thing i changed from my use of this is the VM name at the end. When the function is ran, it will attach all USB devices containing lines with one of '0bb4 0d8c 0424 28de' to your vm 'Steam-WIN10'. USB devices already attached will report errors that we ignore and the ones that aren't attached are attached. If you start running out of USB addresses, then reboot. source mapusb.sh mapusb viveTempFolder '0bb4 0d8c 0424 28de' 'Steam-WIN10'

-- Attached text copy of the script I was using when I last worked on this. mapusb.sh.txt

When I started this guide, the script worked and I had success. The vive was very touchy. As soon as I started to do anything like update firmware or troubleshooting steps, everything went wrong. The Vive software tells the devices to disconnect or reboot because they physically become disconnected from the computer for a moment. When they come back, they are assigned new USB IDs and are not automatically connected back to that VM. I would have to run the script again to reattach the devices at that time. The short of that experiences is: Do not update firmware while doing USB passthough. The trouble shooting steps will cause more headaches too. The officalle best way to do things is to pass the USB controller itself. The new Unraid updates keep your USB Controller passthough settings after you set them within your XML and no longer clear them when you view /edit vm from the GUI. If you can, even if it is temporary, set up your vive / room with USB Controller passthough. Then if you must, switching back to the script approach will be more stable because the vive is already configured on the VM. (Somewhat speculation based on what I can remember) I bought a new ASUS board and that solved all my GPU problems and it had a USB 3.1 controller that I was then able to use for the VIVE. Based on that, I haven't needed to shift back to using USB swapping to running VMS. There is a new plugin "in progress" out there on the "Community Applications" plugin called "Libvirt Hotplug USB". I don't know if that project will be able to handle the Vive when it is done. ___ Speculation: I wonder if Vive passthough would be any better with direct connection to the box instead of using the repeater. One would loose the Bluetooth features of the vive, but that is how the portal VR laptop backpacks are configured. Note: They replace the Vive HDMI because that is special that will only work if connected to repeater box.

After the vive 'disconnects' it readdresses it self as a USB device. so it isn't virtually plugged in anymore. (Catching up on the thread, back from vacation)

First slot pass though sometimes requires telling the video card to load a specified rom that you copied from the card before using a different slot. The video passthough is very touchy. I'm not an expert on the subject as this is my first go. Unraid reports my cards as follows and I have to pass both for the vm to see it. 09:00.0 VGA compatible controller: NVIDIA Corporation Device 17c8 (rev a1) 09:00.1 Audio device: NVIDIA Corporation Device 0fb0 (rev a1) _____ For anyone watching this thread. I had overheating issues and am switching to water cooling. The parts come in September, so I'll resume the build then.

PCI-USB I agree it is possible, but I have several reason why I don't want to do that, including how it would look. how is your core assignment for 4 VMs with 6 cores? 6 cores is 12 Virtual cores to assign due to hyper threading. I'm giving each VM 2-3 virtual cores. Unless the games are designed for multi threading, 2 cores are usually enough for games. I won't be doing multi tasking on the VMs. Each VM will be running only its game. I don't even have Virus scanners on them. (I redo the image every 30 days to keep them clean and I don't browse the internet). Does 1 single core suffice your gaming needs when all the VMs are in use? Each VM will have at least 2 virtual cores out of my 12 virtual cores.

It is possible to run the vive though the VM without a dedicated usb controller. I'm running 4 GPUs without water block modifications. All 7 of my PCIe slots are used / covered. Unless I use a riser PCIe adapter, i won't be able to install a PCIe USB card. With that said, PCIe usb card passthough would defiantly work for the VIVE, but I wouldn't call it a requirement. I prefer being able to hot swap the VIVE between the running VMs. I will be doing a better write up on this for the guide. I made the script generic and posted it to show the concept of I'm doing.

I'm working on a script for dynamic assigning of USB devices to running VMs for my post https://lime-technology.com/forum/index.php?topic=49580.0

Migrating replies from my topic in wrong location. This sounds like exactly what is needed to help polish the USB handling of unraid's KVM management. So as not to duplicate work, I strongly suggest that you email limetech at their support address and point them to this post. I suspect they would be very supportive and possibly offer some suggestions so you don't reinvent the wheel if they already have some of this worked out for an upcoming release. This sounds like exactly what is needed to help polish the USB handling of unraid's KVM management. So as not to duplicate work, I strongly suggest that you email limetech at their support address and point them to this post. I suspect they would be very supportive and possibly offer some suggestions so you don't reinvent the wheel if they already have some of this worked out for an upcoming release. With 4 GPUS, i didn't have any room to add in an additional usb 3 pcie card. For that reason, i ended up having to manage all my USB devices under my existing motherboard usb 2 and usb 3 controllers. The script to migrate usb devices to a running VM simplified the work enough that I didn't bother me to much. On the positive side, this topic will help users with all their pcie slots full.