I've been running VirtualHere more or less successfully on a virtualized debian 32bit system running on a ESXi-server with an attached USB-hub.
Sooner or later (typically 5-10 days) the USB-device (a dongle) becomes unusable and I wonder why or what can be done to keep this from happening.
Restarting the vhusbd won't help in this case, restarting the debian-system has helped one time but today for instance didn't.
This is the log right after rebooting the debian-system:
Wed Dec 2 14:44:11 2015 LOG_INFO >>> Starting v2.6.1 (Built: Nov 25 2015, 11:16:42)<<<
Wed Dec 2 14:44:11 2015 LOG_INFO Using configuration [...SNIP....]/virtualhere/config.ini
Wed Dec 2 14:44:11 2015 LOG_INFO Server licensed to=[...SNIP....] max_devices=unlimited
Wed Dec 2 14:44:11 2015 LOG_INFO Using large URB's
Wed Dec 2 14:44:11 2015 LOG_DEBUG TCPServer starting...
Wed Dec 2 14:44:11 2015 LOG_INFO Listening on all network interfaces at port 7575
Wed Dec 2 14:44:11 2015 LOG_INFO Found Full speed device [...SNIP...] at address 121
Wed Dec 2 14:44:11 2015 LOG_INFO Found Low speed device [...SNIP...] at address 122
Wed Dec 2 14:44:11 2015 LOG_INFO Found Low speed device [096e:0006] "OEM, HID Dongle" at address 123
Wed Dec 2 14:44:12 2015 LOG_INFO Callback: VirtualHere USB Sharing_vhusb_tcplocal Name Registered
Wed Dec 2 14:44:36 2015 LOG_DEBUG 192.168.[...SNIP...] connected
Wed Dec 2 14:45:21 2015 LOG_DEBUG 192.168.[...SNIP...] connected
Wed Dec 2 14:45:54 2015 LOG_ERR Error -1 resetting device 0x096e/0x0006 for capture
Wed Dec 2 14:45:54 2015 LOG_ERR Error binding device 123 to connection 2, BIND_ERROR
On the client-side I get this error displayed in a popup-window upon trying to use the device:
'There was a error sharing this device. (Auto-sharing now off for this device/port)'
When hitting 'OK' here another warning-window pops up with the message
'Error "Operation not permitted" (-1) trying to use this device. (192.168.[...SNIP....]:7575)'
What helps (most likely even without restarting vhusbd or the system) is to pysically re-connect the dongle to the USB-hub after which everything works fine for another couple of days until the scenario repeats.
I've already exchanged the USB-hub and cable with an identical one but the issue stays exactly the same and I fear that whatever is done by VMWare to manage virtual USB-connections may cause these issues.
Do these symptoms ring any bells for someone? Any ideas how to solve it?