vSphere USB Passthru and Autoconnect Devices and PowerCLI
Wait! I thought I had UPS plugged into my host and setup as passthru to my VM already! Why can't I see it now? What happened? Who moved that external drive I had connected to my Veeam console to seed an offsite backup? Ever find yourself asking yourself any of these questions…I certainly have! Due to circumstances out of my control I have a few hosts that tend to be "out in the wild". Available and insecure, readily accessible to the hundreds of people walking by it each day. At time to time either someone trips over a cord, some deliberately unplugs something, or equipment needs to be moved and gets plugged in to different ports upon reconnection.
Not as many options in the GUI
As is with most other products, using the GUI to configure something sometimes doesn't give you all the options that you need. Essentially when configuring USB Passthru to a VM from within either the vSphere Client or the vSphere Web Client you the device needs to be plugged in and it gets assigned to the VM based on the host USB port that it is connected to. Again in most cases this is fine but in my situation I needed to be able to have this device connected to the VM no matter what port it was connected to. Turned out after reading some documentation around the vSphere API as well as having a great discussion with Luc Dekens on the VMTN forums there is indeed a way to do exactly what I needed to do.
Community to the rescue!
So, in the API reference for the VirtualUSBUSBBackingInfo object it states the following
To identify the USB device, you specify an autoconnect pattern for the deviceName. The virtual machine can connect to the USB device if the ESX server can find a USB device described by the autoconnect pattern. The autoconnect pattern consists of name:value pairs. You can use any combination of the following fields.
Perfect, this is exactly what I was looking for. Basically I can have the USB device autoconnect to the VM by initially connecting by using ANY combination of the above parameters as the deviceName. First off, path is out of the question, it's what is going to changed when the device is plugged into a different port. So I decided to use pid, vid, and hostId. Therefore, if a device with the specified product id and vendor id is plugged into a host with the specified hostId it will automatically pass this through to the VM in which I assign it to! Awesome! One problem, I still don't have a clue what the pid, vid, and hostId are, nor do I know the PowerCLI syntax to add the device.
PIDS and VIDS and More…
So how do you find out the pid and vid of the device you want to add? Well, there's a KB for that…kinda, KB1648 mentions how to do it. Basically go to in the Windows registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\ and search around and you'll find it 🙂 In my case i was using an APC SmartUPS 1500 which had a pid and vid of 0003 and 051D respectively.
The final piece of information we need is the hostId. By hostId the documentation really means the actual hardware id that is stored within the BIOS of your host. Accessing ExtensionData.Hardware.Systeminfo.Uuid will actually retrieve this for you. As you will see in the script below there is certainty some formatting issues that need to be resolved with it, but it most certainly works 🙂
Putting it all together
Now that we have all the information we need it's time to fire up PowerCLI to get this task scripted (I needed to do it 40 times 🙂 ). I'm not going to lie here, I had no idea how to do this with PowerCLI but by using Onyx I got a great start.
As you can see in the script below a few things happen. First you need to specify some credentials to and your vCenter location as well as the pid, vid, hostname of the host that will be connected to the device as well as the VM name in which you want to pass the device through. Lines 17 and 18 get some information in regards to the target VM and lines 21 and 22 get that hardware uuid from the host. Lines 24 through 36 is the reformatting of the uuid that I described earlier. You can see the format in the API reference. The rest of the script does the actually setup of the USB device, this is the code, minus a few changes here and there, that Onyx spit out for me.
So there you have it! You can unplug and plug this USB device in to your hearts delight. ESXi should pick up the device no matter what port it is plugged into and pass it on to your VM every time! Certainly this isn't something that you will do everyday, but for those that have hosts sitting out in the open, may be a handy configuration to have set up in their environment. As always, I'm not the greatest scripter in the world, so any comments, suggestions, improvements, concerns, thoughts are most definitely appreciated.