Hi
Yes, the USBarb service is running OK - it is listing the devices and presenting them for connection - when the service was not running, there were no devices listed.
I'm pretty confident that the problem is outside the VMs - I've tried Win7 and Linux, VMs imported from earlier versions and freshly created VMs - the same error comes up every time.
I did update the VMtools in the Win7 VM, and the USB camera is a generic camera that doesn't need special drivers. And from the fact that the Linux machine never sees anything change on the USB bus, I'm also pretty confident that the host never lets workstation/player grab the device at all.
I also tried with all the other USB devices internal to the host (Bluetooth, fingerprint reader and webcam) and they all behave the same - 15 seconds after I try connecting, I get the failed to connect message.
But: Problem Worked Around!
I plugged a USB flash drive in (running VM) and it worked vwithout fuss. And as a bonus, I then could bind the camera in to the VM too... As often as I like.
Shut the machine down, remove the USB flash drive, problem returns - cannot bind devices, same error as before.
Put the USB flash drive back in - it all works again.
Remove the USB flash drive - webcam keeps working.
Disconnect then reconnect the webcam from the VM, it won't reconnect, same error as before.
Then insert USB drive - not only does the flash drive appear, so does the webcam!
(The same is true for inserting any USB device, not just USB flash device)
It is like the message from workstation/player is not been heard by the USBarb service until it gets woken up by something changing on the USB hub, whereupon it binds the device to the VM.
Yuk!
Thanks for your thoughts and ideas on this, hopefully it will help someone else in future too...