VMware Cloud Community
mana690
Contributor
Contributor
‎12-21-2018 04:56 PM

Connect/Disconnect loop with vmware workstation pro 15 and esxi 6.5 on VM guest

Hi all,

i've a little problem with my windows 10 x64 guest on ESXI 6.5, i managed this with vmware workstation pro 15 for the usb passthrough capacity of the soft.

My lab is an unsupported lab, my esxi work on msi X370 pro gamin carbon motherboard, it's work, just the thermal probe monitoring problem but i do with this, it's for personnal works so...

i trying to passthrough an xbox one controller from my latitude d630 laptop where vmware workstation is installed on my windows 10 vm guest, it's work when i plugged the controller with a usb 2.0 cable but with the official cable (3.0 cable), controller performs a connect/disconnect loop on vmware workstation when i connect it on the vm guest.

I tried the "usb.quirks.device0" solution, not work, and i tried to add a usb 3.0 controller on the vm setting, not work also.

i supposed than my dell latitude d630 with 2.0 usb port only can not work properly because the laptop not have a 3.0 controller.

However the controller work properly directy on the laptop with the official cable...

somebody can explain me a solution on this problem or i will have to buy some 2.0 cable to execute the passthrough ?

i copy the loop event on vmware.log here, if can be useful :

vmware.log with usb 3.0 controller on VM guest :

2018-12-22T00:28:10.114Z| vmx| I125: RemoteUSBVMX: Picking a version. Local(15, 16) Remote(15, 16)

2018-12-22T00:28:10.114Z| vmx| I125: USB: Connecting device desc:name:Microsoft\ Controller vid:045e pid:02ea path:1/3/1 host:seb_portable hostId:44\ 45\ 4c\ 4c\ 57\ 00\ 10\ 57-80\ 4a\ ca\ c0\ 4f\ 34\ 34\ 4a speed:full family:vendor instanceId:USB\\VID_0E0F&PID_0001\\3032363030303837373932373532 deviceLocation:remote-client serialnum:3032363030303837373932373532 arbRuntimeKey:a ownerdisplay:10.0.0.1:/vmfs/volumes/5b994523-58023afc-67fa-305a3a5a0e67/Windows_10_X64/Windows_10_X64.vmx version:2 id:0x30000000045e02ea

2018-12-22T00:28:10.114Z| vmx| A100: ConfigDB: Setting usb_xhci:5.fileName = "name:Microsoft\ Controller vid:045e pid:02ea path:1/3/1 host:seb_portable hostId:44\ 45\ 4c\ 4c\ 57\ 00\ 10\ 57-80\ 4a\ ca\ c0\ 4f\ 34\ 34\ 4a speed:full family:vendor virtPath:usb_xhci:5 instanceId:USB\\VID_0E0F&PID_0001\\3032363030303837373932373532 deviceLocation:remote-client serialnum:3032363030303837373932373532 arbRuntimeKey:a ownerdisplay:10.0.0.1:/vmfs/volumes/5b994523-58023afc-67fa-305a3a5a0e67/Windows_10_X64/Windows_10_X64.vmx version:2"

2018-12-22T00:28:10.114Z| vmx| A100: ConfigDB: Setting usb_xhci:5.arbRuntimeKey = "10"

2018-12-22T00:28:10.114Z| vmx| A100: ConfigDB: Setting usb_xhci:5.present = "TRUE"

2018-12-22T00:28:10.114Z| vmx| A100: ConfigDB: Setting usb_xhci:5.deviceType = "remote"

2018-12-22T00:28:10.114Z| vmx| A100: ConfigDB: Setting usb_xhci:5.port = "5"

2018-12-22T00:28:10.114Z| vmx| A100: ConfigDB: Setting usb_xhci:5.parent = "-1"

2018-12-22T00:28:10.115Z| vmx| I125: RemoteUSBVMX: Connected device 0x30000000045e02ea with UUID 52 48 3e 25 d7 5e 36 6e-e2 d9 e3 79 19 fe 0b ce. Using version:16

2018-12-22T00:28:10.115Z| vmx| I125: VUsbUpdateVigorFieldsAndAutoconnect: New set of 1 USB devices

2018-12-22T00:28:10.115Z| vmx| I125: USB: Found device [name:Microsoft\ Controller vid:045e pid:02ea path:1/3/1 host:seb_portable hostId:44\ 45\ 4c\ 4c\ 57\ 00\ 10\ 57-80\ 4a\ ca\ c0\ 4f\ 34\ 34\ 4a speed:full family:vendor virtPath:usb_xhci:5 instanceId:USB\\VID_0E0F&PID_0001\\3032363030303837373932373532 deviceLocation:remote-client serialnum:3032363030303837373932373532 arbRuntimeKey:a ownerdisplay:10.0.0.1:/vmfs/volumes/5b994523-58023afc-67fa-305a3a5a0e67/Windows_10_X64/Windows_10_X64.vmx version:2], connected to usb_xhci port 5.

2018-12-22T00:28:11.597Z| vmx| I125: RemoteUSBVMX: Received pending disconnect for device:0x30000000045e02ea migrating:0

2018-12-22T00:28:14.843Z| vmx| I125: RemoteUSBVMX: Client reconnect from pending disconnect for device:0x30000000045e02ea migrating:0

2018-12-22T00:28:14.843Z| vmx| I125: RemoteUSBVMX: Client sent reconnect string len 192 for device: 0x30000000045e02ea migrating:0

2018-12-22T00:28:14.843Z| vmx| I125: RemoteUSBVMX: Successfully received description for device: 0x30000000045e02ea migrating:0

2018-12-22T00:28:14.843Z| vmx| I125: RemoteUSBVMX: Reconnecting device name:Microsoft\ Controller vid:045e pid:02ea path:1/3/1 host:seb_portable hostId:44\ 45\ 4c\ 4c\ 57\ 00\ 10\ 57-80\ 4a\ ca\ c0\ 4f\ 34\ 34\ 4a speed:full family:vendor deviceType:remote-client

2018-12-22T00:28:14.843Z| vmx| I125: VUsbUpdateVigorFieldsAndAutoconnect: New set of 1 USB devices

2018-12-22T00:28:14.843Z| vmx| I125: USB: Found device [name:Microsoft\ Controller vid:045e pid:02ea path:1/3/1 host:seb_portable hostId:44\ 45\ 4c\ 4c\ 57\ 00\ 10\ 57-80\ 4a\ ca\ c0\ 4f\ 34\ 34\ 4a speed:full family:vendor deviceType:remote-client], connected to usb_xhci port 5.

2018-12-22T00:28:16.988Z| vmx| I125: RemoteUSBVMX: Received pending disconnect for device:0x30000000045e02ea migrating:0

2018-12-22T00:28:19.799Z| vmx| I125: RemoteUSBVMX: Client reconnect from pending disconnect for device:0x30000000045e02ea migrating:0

2018-12-22T00:28:19.799Z| vmx| I125: RemoteUSBVMX: Client sent reconnect string len 192 for device: 0x30000000045e02ea migrating:0

2018-12-22T00:28:19.799Z| vmx| I125: RemoteUSBVMX: Successfully received description for device: 0x30000000045e02ea migrating:0

2018-12-22T00:28:19.799Z| vmx| I125: RemoteUSBVMX: Reconnecting device name:Microsoft\ Controller vid:045e pid:02ea path:1/3/1 host:seb_portable hostId:44\ 45\ 4c\ 4c\ 57\ 00\ 10\ 57-80\ 4a\ ca\ c0\ 4f\ 34\ 34\ 4a speed:full family:vendor deviceType:remote-client

2018-12-22T00:28:19.799Z| vmx| I125: VUsbUpdateVigorFieldsAndAutoconnect: New set of 1 USB devices

vmware.log with usb 2.0 controller on vm guest :

2018-12-22T00:49:59.913Z| vmx| I125: USB: Connecting device desc:name:Microsoft\ Controller vid:045e pid:02ea path:1/3/1 host:seb_portable hostId:44\ 45\ 4c\ 4c\ 57\ 00\ 10\ 57-80\ 4a\ ca\ c0\ 4f\ 34\ 34\ 4a speed:full family:vendor instanceId:USB\\VID_0E0F&PID_0001\\3032363030303837373932373532 deviceLocation:remote-client serialnum:3032363030303837373932373532 arbRuntimeKey:b ownerdisplay:10.0.0.1:/vmfs/volumes/5b994523-58023afc-67fa-305a3a5a0e67/Windows_10_X64/Windows_10_X64.vmx version:2 id:0x30000000045e02ea

2018-12-22T00:49:59.913Z| vmx| A100: ConfigDB: Setting usb:2.fileName = "name:Microsoft\ Controller vid:045e pid:02ea path:1/3/1 host:seb_portable hostId:44\ 45\ 4c\ 4c\ 57\ 00\ 10\ 57-80\ 4a\ ca\ c0\ 4f\ 34\ 34\ 4a speed:full family:vendor virtPath:usb:2 instanceId:USB\\VID_0E0F&PID_0001\\3032363030303837373932373532 deviceLocation:remote-client serialnum:3032363030303837373932373532 arbRuntimeKey:b ownerdisplay:10.0.0.1:/vmfs/volumes/5b994523-58023afc-67fa-305a3a5a0e67/Windows_10_X64/Windows_10_X64.vmx version:2"

2018-12-22T00:49:59.913Z| vmx| A100: ConfigDB: Setting usb:2.arbRuntimeKey = "11"

2018-12-22T00:49:59.913Z| vmx| A100: ConfigDB: Setting usb:2.present = "TRUE"

2018-12-22T00:49:59.913Z| vmx| A100: ConfigDB: Setting usb:2.deviceType = "remote"

2018-12-22T00:49:59.913Z| vmx| A100: ConfigDB: Setting usb:2.port = "0"

2018-12-22T00:49:59.913Z| vmx| A100: ConfigDB: Setting usb:2.parent = "1"

2018-12-22T00:49:59.915Z| vmx| I125: RemoteUSBVMX: Connected device 0x30000000045e02ea with UUID 52 61 1d b7 f5 52 ff 97-66 01 d7 12 81 11 86 9e. Using version:16

2018-12-22T00:49:59.915Z| vmx| I125: VUsbUpdateVigorFieldsAndAutoconnect: New set of 1 USB devices

2018-12-22T00:49:59.915Z| vmx| I125: USB: Found device [name:Microsoft\ Controller vid:045e pid:02ea path:1/3/1 host:seb_portable hostId:44\ 45\ 4c\ 4c\ 57\ 00\ 10\ 57-80\ 4a\ ca\ c0\ 4f\ 34\ 34\ 4a speed:full family:vendor virtPath:usb:2 instanceId:USB\\VID_0E0F&PID_0001\\3032363030303837373932373532 deviceLocation:remote-client serialnum:3032363030303837373932373532 arbRuntimeKey:b ownerdisplay:10.0.0.1:/vmfs/volumes/5b994523-58023afc-67fa-305a3a5a0e67/Windows_10_X64/Windows_10_X64.vmx version:2], connected to usb:1 port 0.

2018-12-22T00:50:01.905Z| vmx| I125: RemoteUSBVMX: Received pending disconnect for device:0x30000000045e02ea migrating:0

2018-12-22T00:50:03.489Z| vmx| I125: RemoteUSBVMX: Client reconnect from pending disconnect for device:0x30000000045e02ea migrating:0

2018-12-22T00:50:03.489Z| vmx| I125: RemoteUSBVMX: Client sent reconnect string len 192 for device: 0x30000000045e02ea migrating:0

2018-12-22T00:50:03.489Z| vmx| I125: RemoteUSBVMX: Successfully received description for device: 0x30000000045e02ea migrating:0

2018-12-22T00:50:03.489Z| vmx| I125: RemoteUSBVMX: Reconnecting device name:Microsoft\ Controller vid:045e pid:02ea path:1/3/1 host:seb_portable hostId:44\ 45\ 4c\ 4c\ 57\ 00\ 10\ 57-80\ 4a\ ca\ c0\ 4f\ 34\ 34\ 4a speed:full family:vendor deviceType:remote-client

2018-12-22T00:50:03.489Z| vmx| I125: VUsbUpdateVigorFieldsAndAutoconnect: New set of 1 USB devices

2018-12-22T00:50:03.489Z| vmx| I125: USB: Found device [name:Microsoft\ Controller vid:045e pid:02ea path:1/3/1 host:seb_portable hostId:44\ 45\ 4c\ 4c\ 57\ 00\ 10\ 57-80\ 4a\ ca\ c0\ 4f\ 34\ 34\ 4a speed:full family:vendor deviceType:remote-client], connected to usb:1 port 0.

2018-12-22T00:50:04.543Z| vmx| W115: USB: Device 0x30000000045e02ea has config 1, interface 0 defined multiple times

2018-12-22T00:50:05.924Z| vmx| I125: RemoteUSBVMX: Received pending disconnect for device:0x30000000045e02ea migrating:0

2018-12-22T00:50:08.523Z| vmx| I125: RemoteUSBVMX: Client reconnect from pending disconnect for device:0x30000000045e02ea migrating:0

2018-12-22T00:50:08.523Z| vmx| I125: RemoteUSBVMX: Client sent reconnect string len 192 for device: 0x30000000045e02ea migrating:0

2018-12-22T00:50:08.523Z| vmx| I125: RemoteUSBVMX: Successfully received description for device: 0x30000000045e02ea migrating:0

2018-12-22T00:50:08.523Z| vmx| I125: RemoteUSBVMX: Reconnecting device name:Microsoft\ Controller vid:045e pid:02ea path:1/3/1 host:seb_portable hostId:44\ 45\ 4c\ 4c\ 57\ 00\ 10\ 57-80\ 4a\ ca\ c0\ 4f\ 34\ 34\ 4a speed:full family:vendor deviceType:remote-client

2018-12-22T00:50:08.523Z| vmx| I125: VUsbUpdateVigorFieldsAndAutoconnect: New set of 1 USB devices

i have the same story with a Windows 7 X64 guest.

EDIT :  i also tried the usb power setting tips on windows, the problem is the same.

Thanks for your help and excuse me for my language, i'm bad in english.

0 Kudos
1 Reply
mana690
Contributor
Contributor
‎12-22-2018 04:19 PM

Hi

So i've advanced a little on my problem.

it seems the standard xbox one controller pad which have a loop connect/disconnect, the xbox 360 and xbox one elite don't connect/disconnect continually and change the cable have no effect on this loop bug.

the standard xbox one controller have a pid of 02ea and the xbox one elite controller have a pid of 02e3, the vid is the same for the 3 device : 045e

why the usb over ip work with the xbox one elite controller and not with the standard xbox one controller ? the pid is very similar...

I had also some issue with my kfa 2 gtx 970 passthrough, but with the "hypervisor.cpuid.v0" value and a windows 10 vm... and a short downclocking of the gpu, the passthrough seems work perfecty (i had most frequently direct x crash before the downcloking...however my power supply is a corsair 750W model so i don't explain why the gpu needed a downclocking but it work so...).

do you have some points where i can investigate to resolve this connect/disconnect loop ? or i must sell my xbox one controller and search a xbox 360 controller pad on the web ?

thanks for your suggestions.

0 Kudos