Location
  • York,
  • England,
  • United Kingdom

Top Contributors

VMware Support Test - for USB Passthrough issue

Based on this article

HOW TO: Add and Connect a USB Device to a Virtual Machine, hosted on VMware vSphere Hypervisor ESX 4.1 ESXi 4.1, ESXi 5.0

A follow-up to this article, with the rise of VMware Administrators trying to connect, USB devices to ESXi host servers, and finding that they are not available for USB passthrough, although they are visible to the ESXi Host Hypervisor, (check with dmesg or cat /var/vmkernel.log | grep usb), so software fudge is not displaying them in the vCenter Server passthrough, with recent issues with USB Passthrough and the following error messages...

When trying to connect two Security Keys (dongles) that have worked for many years to a VM, the following appears:-

Cannot connect "path:1/0/3 host:esxi004..ac.uk deviceLocation:remote-host version:2" to this virtual machine. The device was not found.

Cannot connect "path:2/0/1 version:2" to this virtual machine. The device was not found.

This was working, it does not work across any hosts.

The security keys are Aladdin Knowledge HASP HL 3.25Aladdin Knowledge HASP HL 3.25 as available in he devices.



Production is down, because NO body at the university can run the applications, because these network keys are unavailable, as a network license!

We thought we would escalate this to VMware Support and test them, and I'll document here....

Support Request Confirmation Number:157zzzzzz108
Support Request Status:Open (Unassigned)
Date and Time Created:2015-08-04 10:41
Target Response Time: 2015-08-04 14:42 (GMT+00:00) GMT Standard Time

Waiting....

Servers Are:-

ESXi 5.5 Build 2718055 on 8 ESXi Hosts. Running on Dell R710/R720 hardware.

vCenter Server Build 5.5.0 2646482.

HASP keys are:-

2015-08-04T10:01:12.971Z cpu8:33553)<6>usb 1-1.4: new low speed USB device number 9 using ehci_hcd
2015-08-04T10:01:13.095Z cpu15:33553)<6>usb 1-1.4: New USB device found idVendor=0529 idProduct=0001
2015-08-04T10:01:13.095Z cpu15:33553)<6>usb 1-1.4: New USB device strings: Mfr=1 Product=2 SerialNumber=0
2015-08-04T10:01:13.095Z cpu15:33553)<6>usb 1-1.4: Product: HASP HL 3.25
2015-08-04T10:01:13.095Z cpu15:33553)<6>usb 1-1.4: Manufacturer: AKS
2015-08-04T10:01:13.096Z cpu15:33553)<6>usb 1-1.4: usbfs: registered usb0109

2015-08-04T10:06:09.969Z cpu18:33553)<6>usb 2-1.2: new low speed USB device number 8 using ehci_hcd
2015-08-04T10:06:10.090Z cpu18:33553)<6>usb 2-1.2: New USB device found idVendor=0529 idProduct=0001
2015-08-04T10:06:10.090Z cpu18:33553)<6>usb 2-1.2: New USB device strings: Mfr=1 Product=2 SerialNumber=0
2015-08-04T10:06:10.090Z cpu18:33553)<6>usb 2-1.2: Product: HASP HL 3.25
2015-08-04T10:06:10.090Z cpu18:33553)<6>usb 2-1.2: Manufacturer: AKS
2015-08-04T10:06:10.090Z cpu18:33553)<6>usb 2-1.2: usbfs: registered usb0208


We also have a follow-on question related to USB Passthrough.... the following devices do not appear as USB passthrough devices for the virtual machine but they are recognised by the host?

WHY?

2015-08-04T10:17:15.038Z cpu4:33553)<6>usb 1-1.5: new high speed USB device number 11 using ehci_hcd
2015-08-04T10:17:15.155Z cpu4:33553)<6>usb 1-1.5: New USB device found idVendor=19d2 idProduct=0103
2015-08-04T10:17:15.155Z cpu4:33553)<6>usb 1-1.5: New USB device strings: Mfr=3 Product=2 SerialNumber=4
2015-08-04T10:17:15.155Z cpu4:33553)<6>usb 1-1.5: Product: ZTE WCDMA Technologies MSM
2015-08-04T10:17:15.155Z cpu4:33553)<6>usb 1-1.5: Manufacturer: ZTE Incorporated
2015-08-04T10:17:15.155Z cpu4:33553)<6>usb 1-1.5: SerialNumber: P6zzzzzzzz000
2015-08-04T10:17:15.158Z cpu4:33553)<6>usb 1-1.5: Vendor: 0x19d2 Product: 0x0103 Revision: 0x0000
2015-08-04T10:17:15.158Z cpu4:33553)<6>usb 1-1.5: Interface Subclass: 0x06 Protocol: 0x50

2015-08-04T10:04:13.718Z cpu15:33553)<6>usb 1-1.5: new high speed USB device number 10 using ehci_hcd
2015-08-04T10:04:13.836Z cpu15:33553)<6>usb 1-1.5: New USB device found idVendor=2357 idProduct=f000
2015-08-04T10:04:13.836Z cpu15:33553)<6>usb 1-1.5: New USB device strings: Mfr=3 Product=2 SerialNumber=4
2015-08-04T10:04:13.836Z cpu15:33553)<6>usb 1-1.5: Product: TP-LINK HSPA+ Modem
2015-08-04T10:04:13.836Z cpu15:33553)<6>usb 1-1.5: Manufacturer: TP-LINK Incorporated
2015-08-04T10:04:13.836Z cpu15:33553)<6>usb 1-1.5: SerialNumber: 863zzzzzz34668
2015-08-04T10:04:13.903Z cpu15:33553)<6>usb 1-1.5: Vendor: 0x2357 Product: 0xf000 Revision: 0x0000
2015-08-04T10:04:13.903Z cpu15:33553)<6>usb 1-1.5: Interface Subclass: 0x06 Protocol: 0x50

This VMware Support call is flagged as PRODUCTION DOWN!
View Previous CommentsLoad All Comments (11)
Rank: Elite

Author Comment

Just to finish off this......

Call open with VMware on the 4 August 2015

today I received this

I hope you are well.

I have reviewed the logs that you have uploaded to the case. At this point there is nothing that points out why you ran into this issue.
At this point I have also contacted support to have this KB updated. That is a  work in progress and will be carried out. Please note this will be later rather than sooner at this point.

For now I suggest that we archive this case. To follow the KB updates I would suggest subscribing to the KB for updates.

So if you have no further questions I will proceed to archive the case as resolved later today.

I look forward to hearing from you.

So three weeks later, and we still have no idea, so things happen, with no reason why!

But the KB Article will be updated, we will see.
0

Expert Comment

JHMH IT Staff2016-03-04 03:24 PMID: 1898696
Interesting to see this; does this issue also occur in View? I have a Sentinel security dongle for Alpha Card software I was trying to connect through a linux-based thin client, and I assumed it was a limitation of the client (I have not yet tested on a PCoIP zero client).
0
Rank: Elite

Author Comment

where is the USB device connected to client or host ?
0

Expert Comment

JHMH IT Staff2016-03-04 05:30 PMID: 1898717
To the client, using the Horizon View Connection agent for Wyse Linux, specifically on a Wyse D50D. I have not tested the dongle on a Teradici based zero client yet.
0
Rank: Elite

Author Comment

Okay, USB Passthrough at the Client is handled very differently to Host passthrough, it uses the technology from VMware Workstation, so all if not all USB devices should passthrough.

Unless, there is some middle ware which prevents this!
0

Expert Comment

JHMH IT Staff2016-03-04 05:46 PMID: 1898726
I believe it's because of how the Wyse  linux-based clients handle devices, namely it needs drivers similar to passing a USB connection through Windows to a console session. This issue also affects biometric readers for Impravada, and because we're currently using the Wyse thin clients in areas the biometric readers would be needed the entire project was scrapped.

I'll test the dongle next week on a zero client and report back; based on this discussion I expect a more positive result.
0