When you add a USB device connection from an ESXi host to a virtual machine, the autoconnect feature is enabled for the device connection. It is not disabled until you remove the device connection from the virtual machine.
- The virtual machine is cycling through power operations, such as Power Off/Power On, Reset, Pause/Resume.
- The device is unplugged from the host then plugged back in to the same USB port.
- The device is power cycled but has not changed its physical connection path.
- The device is mutating identity during usage.
- A new virtual USB device is added
The USB passthrough autoconnect feature identifies the device by using the USB path of the device on the host. It uses the physical topology and port location, rather than the device identity. This feature can seem confusing if you expect the autoconnect feature to match the connection target by device ID.
If the same device is plugged back in to the host through a different USB port, it cannot re-establish connection with the virtual machine. If you unplug the device from the host and plug in a different device to the same USB path, the new device appears and is connected to the virtual machine by the autoconnect feature that the previous device connection enabled.
Autoconnect is useful in cases where devices mutate during usage. For example, for iPhones and other such devices, the device VID:PID changes during software or firmware upgrades. The upgrade process disconnects and reconnects the devices to the USB port.
The USB port is speed-specific. The autoconnect feature might not work if you change a USB device with another USB device that works with different speed. For example, you might connect a USB 2.0 high-speed device to a port and connect that device to the virtual machine. If you unplug the device from the host and plug a USB 1.1 or USB 3.0 device into the same port, the device might not connect to the virtual machine.
For a list of supported USB devices for passthrough from an ESXi host to a virtual machine, see the VMware knowledge base article at http://kb.vmware.com/kb/1021345.