GD,
Thanks for the feedback! I also used 14320388 with 3 same type adapters, and it just works fine with the new build. From the log you just shared, I can see the device is reattached (attached/deteched/attach again). Can you help to double check the connection and try again?
Thanks,
Songtao
vmware -vl
VMware ESXi 6.7.0 build-14320388
VMware ESXi 6.7.0 Update 3
Hi Sangtao,
I unplugged and plugged the usb adapter, but the issue is when there is traffic, the nic goes down:
2019-10-14T06:40:57.841Z cpu2:2097560)cdce_attach: usbd_transfer_setup success with alt 1
2019-10-14T06:40:57.842Z cpu0:2097573)DMA: 679: DMA Engine 'vusb0-dma-engine' created using mapper 'DMANull'.
2019-10-14T06:40:57.842Z cpu0:2097573)Uplink: 13962: Opening device vusb0
2019-10-14T06:40:57.842Z cpu2:2097208)Uplink: 13811: Detected pseudo-NIC for 'vusb0'
2019-10-14T06:41:02.648Z cpu1:2097208)NetqueueBal: 4967: vusb0: new netq module, reset logical space needed
2019-10-14T06:41:02.648Z cpu1:2097208)NetqueueBal: 4996: vusb0: plugins to call differs, reset logical space
2019-10-14T06:41:02.648Z cpu1:2097208)NetqueueBal: 5032: vusb0: device Up notification, reset logical space needed
2019-10-14T06:41:02.648Z cpu1:2213748)NetSched: 654: vusb0-0-tx: worldID = 2213748 exits
2019-10-14T06:44:37.281Z cpu1:2097560)DMA: 724: DMA Engine 'vusb0-dma-engine' destroyed.
2019-10-14T06:44:37.281Z cpu1:2213756)NetSched: 654: vusb0-0-tx: worldID = 2213756 exits
2019-10-14T06:44:37.281Z cpu1:2097560)WARNING: usb_proc_free:249: failed to destroy world 2213746: Not found
v1.1 always assume the link is up, and in v1.2, The driver adds the link connection and speed detection by reading interrupt endpoint. If it get the feedback with link connection notification with disconnected, the driver will report link down to uplink layer. I suspect we got the link connection down notification. Can you check the cable? is the led still blinking? how about plugging unplugging the cable? I have 5 such devices which work fine and I have not seen such issue, and I can try more.
Hi Sangtao,
The link is always up and remains up when issue occur. Issue is when there is traffic, the nic goes down. This is my log. The usb adapter is Qilive USB 3.0/Cat5e Network Adapter Q.9575. Maybe is cheaper adapter with Realtek chipset.
2019-10-15T19:25:06.071Z cpu1:2097560)cdce_attach: usbd_transfer_setup success with alt 1
2019-10-15T19:25:06.072Z cpu2:2097573)DMA: 679: DMA Engine 'vusb0-dma-engine' created using mapper 'DMANull'.
2019-10-15T19:25:06.072Z cpu2:2097573)Uplink: 13962: Opening device vusb0
2019-10-15T19:25:06.072Z cpu1:2097208)Uplink: 13811: Detected pseudo-NIC for 'vusb0'
2019-10-15T19:25:15.240Z cpu3:2097208)NetqueueBal: 4967: vusb0: new netq module, reset logical space needed
2019-10-15T19:25:15.240Z cpu3:2097208)NetqueueBal: 4996: vusb0: plugins to call differs, reset logical space
2019-10-15T19:25:15.240Z cpu3:2097208)NetqueueBal: 5032: vusb0: device Up notification, reset logical space needed
2019-10-15T19:25:15.240Z cpu1:2229290)NetSched: 654: vusb0-0-tx: worldID = 2229290 exits
[root@esxi5:~]
[root@esxi5:~]
[root@esxi5:~] esxcli network nic list
Name PCI Device Driver Admin Status Link Status Speed Duplex MAC Address MTU Description
------ ------------ ------ ------------ ----------- ----- ------ ----------------- ---- ------------------------------------------------
vmnic0 0000:00:1f.6 ne1000 Up Up 1000 Full 94:c6:91:1e:f0:6f 1500 Intel Corporation Ethernet Connection (4) I219-V
vusb0 Pseudo uether Up Down 0 Half 00:e0:4c:68:00:18 1500 Realtek USB 101001000 LAN
[root@esxi5:~] esxcli network nic list
Name PCI Device Driver Admin Status Link Status Speed Duplex MAC Address MTU Description
------ ------------ ------ ------------ ----------- ----- ------ ----------------- ---- ------------------------------------------------
vmnic0 0000:00:1f.6 ne1000 Up Up 1000 Full 94:c6:91:1e:f0:6f 1500 Intel Corporation Ethernet Connection (4) I219-V
vusb0 Pseudo uether Up Up 1000 Full 00:e0:4c:68:00:18 1500 Realtek USB 101001000 LAN
-------------------------
2019-10-15T19:38:00.256Z cpu1:2097208)NetqueueBal: 4967: vusb0: new netq module, reset logical space needed
2019-10-15T19:38:00.256Z cpu1:2097208)NetqueueBal: 4996: vusb0: plugins to call differs, reset logical space
2019-10-15T19:38:00.256Z cpu1:2097208)NetqueueBal: 5032: vusb0: device Up notification, reset logical space needed
2019-10-15T19:38:00.256Z cpu0:2229703)NetSched: 654: vusb0-0-tx: worldID = 2229703 exits
2019-10-15T19:38:01.759Z cpu2:2097560)DMA: 724: DMA Engine 'vusb0-dma-engine' destroyed.
2019-10-15T19:38:01.759Z cpu1:2229712)NetSched: 654: vusb0-0-tx: worldID = 2229712 exits
2019-10-15T19:38:01.759Z cpu2:2097560)WARNING: usb_proc_free:249: failed to destroy world 2229701: Not found
2019-10-15T19:38:02.563Z cpu2:2097560)cdce_attach: usbd_transfer_setup success with alt 1
2019-10-15T19:38:02.563Z cpu0:2097573)DMA: 679: DMA Engine 'vusb0-dma-engine' created using mapper 'DMANull'.
2019-10-15T19:38:02.563Z cpu0:2097573)Uplink: 13962: Opening device vusb0
2019-10-15T19:38:02.564Z cpu2:2097208)Uplink: 13811: Detected pseudo-NIC for 'vusb0'
2019-10-15T19:38:12.256Z cpu2:2097208)NetqueueBal: 4967: vusb0: new netq module, reset logical space needed
2019-10-15T19:38:12.256Z cpu2:2097208)NetqueueBal: 4996: vusb0: plugins to call differs, reset logical space
2019-10-15T19:38:12.256Z cpu2:2097208)NetqueueBal: 5032: vusb0: device Up notification, reset logical space needed
2019-10-15T19:38:12.256Z cpu2:2229717)NetSched: 654: vusb0-0-tx: worldID = 2229717 exits
2019-10-15T19:38:17.765Z cpu2:2097560)DMA: 724: DMA Engine 'vusb0-dma-engine' destroyed.
2019-10-15T19:38:17.765Z cpu3:2229727)NetSched: 654: vusb0-0-tx: worldID = 2229727 exits
2019-10-15T19:38:17.765Z cpu0:2097560)WARNING: usb_proc_free:249: failed to destroy world 2229715: Not found
2019-10-15T19:38:18.570Z cpu2:2097560)cdce_attach: usbd_transfer_setup success with alt 1
2019-10-15T19:38:18.571Z cpu0:2097573)DMA: 679: DMA Engine 'vusb0-dma-engine' created using mapper 'DMANull'.
2019-10-15T19:38:18.571Z cpu0:2097573)Uplink: 13962: Opening device vusb0
2019-10-15T19:38:18.571Z cpu0:2097208)Uplink: 13811: Detected pseudo-NIC for 'vusb0'
2019-10-15T19:38:28.256Z cpu1:2097208)NetqueueBal: 4967: vusb0: new netq module, reset logical space needed
2019-10-15T19:38:28.256Z cpu1:2097208)NetqueueBal: 4996: vusb0: plugins to call differs, reset logical space
2019-10-15T19:38:28.256Z cpu1:2097208)NetqueueBal: 5032: vusb0: device Up notification, reset logical space needed
2019-10-15T19:38:28.256Z cpu0:2229732)NetSched: 654: vusb0-0-tx: worldID = 2229732 exits
2019-10-15T19:44:17.418Z cpu3:2097560)DMA: 724: DMA Engine 'vusb0-dma-engine' destroyed.
2019-10-15T19:44:17.418Z cpu3:2229741)NetSched: 654: vusb0-0-tx: worldID = 2229741 exits
2019-10-15T19:44:17.418Z cpu2:2097560)WARNING: usb_proc_free:249: failed to destroy world 2229730: Not found
[root@esxi5:~] esxcli network nic list
Name PCI Device Driver Admin Status Link Status Speed Duplex MAC Address MTU Description
------ ------------ ------ ------------ ----------- ----- ------ ----------------- ---- ------------------------------------------------
vmnic0 0000:00:1f.6 ne1000 Up Up 1000 Full 94:c6:91:1e:f0:6f 1500 Intel Corporation Ethernet Connection (4) I219-V
Thanks GD, Interestingly, I still can see the USB NIC device is detach and reattach on the USB bus, that is why we see the driver is reclaim the device over again. One normal reason is the signal on the USB bus is not stable enough. It can be affect by the USB device, cable, power, and even other USB devices. Is there any other USB devices on the USB bus also? Do you have other USB NIC devices to try?
Thanks,
Songtao
Hi Sangtao, I decided to buy some tp-link U300 network adapter and using instead of this 3 of cheapest network adapters. No problem with TP-link network adapter. Thank you again for support.
But I have no issue with the same RTL8153 Gigabit Ethernet Adapter on esxi 6.7 update 2 and ver 1.1 driver:
[root@esxi6:~] vmware -vl
VMware ESXi 6.7.0 build-13006603
VMware ESXi 6.7.0 Update 2
[root@esxi6:~] esxcli software vib get | grep fling
VMW_bootbank_vmkusb-nic-fling_2.0-1vmw.670.2.48.24524132
Name: vmkusb-nic-fling
[root@esxi6:~] localcli system module list | grep usb
vmkusb_nic_fling true true
[root@esxi6:~] lsusb
Bus 001 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter
Bus 001 Device 001: ID 0e0f:8003 VMware, Inc. Root Hub
[root@esxi6:~] esxcli network nic list
Name PCI Device Driver Admin Status Link Status Speed Duplex MAC Address MTU Description
------ ------------ ------ ------------ ----------- ----- ------ ----------------- ---- ------------------------------------------------
vmnic0 0000:00:1f.6 ne1000 Up Up 1000 Full 94:c6:91:a6:e9:52 1500 Intel Corporation Ethernet Connection (6) I219-V
vusb0 Pseudo uether Up Up 1000 Full 00:e0:4c:68:00:18 1500 Realtek USB 101001000 LAN
[root@esxi6:~] dmesg | grep usb
2019-09-30T21:16:08.555Z cpu0:2097152)VisorFSTar: 1856: net_usbn.v00 for 0xd500 bytes
2019-09-30T21:16:08.565Z cpu0:2097152)VisorFSTar: 1856: ohci_usb.v00 for 0xffc8 bytes
2019-09-30T21:16:08.591Z cpu0:2097152)VisorFSTar: 1856: uhci_usb.v00 for 0xfe50 bytes
2019-09-30T21:16:08.591Z cpu0:2097152)VisorFSTar: 1856: usb_stor.v00 for 0x288f0 bytes
2019-09-30T21:16:08.591Z cpu0:2097152)VisorFSTar: 1856: usbcore_.v00 for 0x4f948 bytes
2019-09-30T21:16:08.594Z cpu0:2097152)VisorFSTar: 1856: vmkusb_n.v00 for 0x1798b8 bytes
2019-09-30T21:16:08.597Z cpu0:2097152)VisorFSTar: 1856: vmkusb.v00 for 0xf5400 bytes
2019-09-30T21:16:12.545Z cpu2:2097546)Loading module vmkusb_nic_fling ...
2019-09-30T21:16:12.546Z cpu2:2097546)Elf: 2101: module vmkusb_nic_fling has license VMware
2019-09-30T21:16:12.555Z cpu2:2097546)Device: 192: Registered driver 'vmkusb_nic_fling' from 20
2019-09-30T21:16:12.555Z cpu2:2097546)Mod: 4962: Initialization of vmkusb_nic_fling succeeded with module ID 20.
2019-09-30T21:16:12.555Z cpu2:2097546)vmkusb_nic_fling loaded successfully.
2019-09-30T21:16:12.625Z cpu3:2097535)Device: 327: Found driver vmkusb_nic_fling for device 0x11e4430445e3885a
2019-09-30T21:16:13.469Z cpu1:2097500)Activating Jumpstart plugin usb.
2019-09-30T21:16:13.587Z cpu2:2097590)Loading module usb ...
2019-09-30T21:16:13.587Z cpu2:2097590)Elf: 2101: module usb has license GPL
2019-09-30T21:16:13.589Z cpu2:2097590)module heap vmklnx_usb: Initial heap size = 262144, max heap size = 13860864
2019-09-30T21:16:13.589Z cpu2:2097590)module heap vmklnx_usb: using memType 2
2019-09-30T21:16:13.589Z cpu2:2097590)module heap vmklnx_usb: creation succeeded. id = 0x43085d9d2000
2019-09-30T21:16:13.589Z cpu2:2097590)<6>usbcore: registered new interface driver usbfs
2019-09-30T21:16:13.589Z cpu2:2097590)WARNING: CharDriver: 356: Driver with name usbdevices is already using slot 48
2019-09-30T21:16:13.589Z cpu2:2097590)usbfs: failed to register usbdevices (-16)
2019-09-30T21:16:13.589Z cpu2:2097590)<6>usbcore: removing devices
2019-09-30T21:16:13.589Z cpu2:2097590)<6>usbcore: cleaning up devio
2019-09-30T21:16:13.589Z cpu2:2097590)<6>usbcore: degistering usbfs_driver
2019-09-30T21:16:13.589Z cpu2:2097590)<6>usbcore: deregistering interface driver usbfs
2019-09-30T21:16:13.589Z cpu2:2097590)<6>usbcore: cleaning up major
2019-09-30T21:16:13.589Z cpu2:2097590)<6>usbcore: unregistering notifier
2019-09-30T21:16:13.589Z cpu2:2097590)<6>usbcore: unregistering bus
2019-09-30T21:16:13.589Z cpu2:2097590)<6>usbcore: cleaning up debugfs
2019-09-30T21:16:13.589Z cpu2:2097590)<6>usbcore: Failed to initialize USB
2019-09-30T21:16:13.589Z cpu2:2097590)usb failed to load.
2019-09-30T21:16:13.589Z cpu2:2097590)WARNING: Elf: 3144: Kernel based module load of usb failed: Failure <Mod_LoadDone failed>
2019-09-30T21:16:13.593Z cpu1:2097500)Jumpstart plugin usb activation failed: usb->start() failed: exited with code 1
2019-09-30T21:16:16.041Z cpu2:2097560)usbd_setup_device_desc:1987: getting device descriptor at addr 2 failed, USB_ERR_IOERROR
2019-09-30T21:16:17.355Z cpu0:2097560)usbd_setup_device_desc:1987: getting device descriptor at addr 2 failed, USB_ERR_IOERROR
2019-09-30T21:16:19.174Z cpu0:2097560)usbd_setup_device_desc:1987: getting device descriptor at addr 2 failed, USB_ERR_IOERROR
2019-09-30T21:16:20.490Z cpu0:2097560)usbd_setup_device_desc:1987: getting device descriptor at addr 2 failed, USB_ERR_IOERROR
2019-09-30T21:16:22.313Z cpu2:2097560)usbd_setup_device_desc:1987: getting device descriptor at addr 2 failed, USB_ERR_IOERROR
2019-09-30T21:18:10.878Z cpu0:2098188)Starting service usbarbitrator
2019-09-30T21:18:10.879Z cpu0:2098188)Activating Jumpstart plugin usbarbitrator.
2019-09-30T21:18:20.967Z cpu0:2098188)Jumpstart plugin usbarbitrator activated.
2019-10-01T18:45:32.358Z cpu0:2097569)Uplink: 11671: Device vusb0 not yet opened
2019-10-01T18:45:32.358Z cpu0:2097569)DMA: 679: DMA Engine 'vusb0-dma-engine' created using mapper 'DMANull'.
2019-10-01T18:45:32.358Z cpu0:2097569)Uplink: 13950: Opening device vusb0
2019-10-01T18:45:32.358Z cpu2:2097208)Uplink: 13799: Detected pseudo-NIC for 'vusb0'
2019-10-01T18:45:36.633Z cpu3:2097208)NetqueueBal: 4967: vusb0: new netq module, reset logical space needed
2019-10-01T18:45:36.633Z cpu3:2097208)NetqueueBal: 4996: vusb0: plugins to call differs, reset logical space
2019-10-01T18:45:36.633Z cpu3:2097208)NetqueueBal: 5032: vusb0: device Up notification, reset logical space needed
2019-10-01T18:45:36.633Z cpu0:2144860)NetSched: 654: vusb0-0-tx: worldID = 2144860 exits
2019-10-01T18:56:52.006Z cpu3:2097560)DMA: 724: DMA Engine 'vusb0-dma-engine' destroyed.
2019-10-01T18:56:52.006Z cpu0:2144866)NetSched: 654: vusb0-0-tx: worldID = 2144866 exits
2019-10-01T18:56:52.006Z cpu3:2097560)WARNING: usb_proc_free:249: failed to destroy world 2144858: Not found
2019-10-01T18:56:52.811Z cpu0:2097569)DMA: 679: DMA Engine 'vusb0-dma-engine' created using mapper 'DMANull'.
2019-10-01T18:56:52.811Z cpu0:2097569)Uplink: 13950: Opening device vusb0
2019-10-01T18:56:52.811Z cpu3:2097208)Uplink: 13799: Detected pseudo-NIC for 'vusb0'
2019-10-01T18:56:57.648Z cpu3:2097208)NetqueueBal: 4967: vusb0: new netq module, reset logical space needed
2019-10-01T18:56:57.648Z cpu3:2097208)NetqueueBal: 4996: vusb0: plugins to call differs, reset logical space
2019-10-01T18:56:57.648Z cpu3:2097208)NetqueueBal: 5032: vusb0: device Up notification, reset logical space needed
2019-10-01T18:56:57.648Z cpu2:2145181)NetSched: 654: vusb0-0-tx: worldID = 2145181 exits
2019-10-01T18:57:48.029Z cpu3:2097560)DMA: 724: DMA Engine 'vusb0-dma-engine' destroyed.
2019-10-01T18:57:48.029Z cpu0:2145194)NetSched: 654: vusb0-0-tx: worldID = 2145194 exits
2019-10-01T18:57:48.029Z cpu3:2097560)WARNING: usb_proc_free:249: failed to destroy world 2145179: Not found
I have what sounds like the same problem. I have installed on ESXi702 and am using an HP USB NIC which has the RTL8153 chipset. After a period of somewhere between 1-3 days, it stops responding but unplugging and re-plugging into USB-C socket fixes it. Have now tried two link cables the latter of which has been working on my firewall for years. I don't believe its the link cable.
Is there any point updating to 703 and the 703 driver or is buying a different NIC the best approach? Any recommendations for a cheap NIC which is reliable in this situation?
TIA
Wallport
Ha - looks like 703 was pulled so ignore that. So, is a TP-Link U300 the best option for reliability?
TIA
An update - I plugged the USB NIC into a different port using a USB-C to USB-A adapter and it has now been stable for longer than it ever lasted before. The USB-A port is 3.1 Gen 1 versus the USB-C port which was 3.1 gen 2 - maybe this is why?
Are there any known issues with the fling driver?
...and looking at the specs of the TP-Link U300 its based on the same RTL8153 chipset so maybe someone has another recommendation?
TIA
Why ESXi not support onboard realtec nics? F.e. RTL8168. I have it on a motherboard, but can't use it. A third-party driver allowed to run this. But the speed is limited to 100mbits. It is very sad.
Hello everybody,
I have a TP-Link UE300 and when I install the driver on ESXi 6.7U2 or U3, I see "vusb1" even if the adapter is not plugged in. The speed remains at 1000, whether a cable is connected or not. What can I do now? I am using an Intel NUC8I3BEK2.
Thank you in advance for your help!
the 1.2 version has added the speed and cable connection support. Would you please have a try?
Thanks,
Songtao
Hello Everyone and thanks for this wonderful driver/module for ESXi 6.7
anyway, I was using the old r8152 module with ESXi 6.7u1 until I faced some high CPU on system process after a few uptime days ... then I decided to move on to 6.7u2 as this was supposed to be resolved.
I disabled the r8152 module then uninstalled it, and went for the upgrade to 6.7u2.
Everything went fine then I wanted to add this new driver/module, which I did, but, vusb0 pops up in the Physical NICs section, but I can't seem to get communication with outside world now.
I reverted back to the old r8152 but still working fine as per 6.7u2 it seems.
Anyway, Can you please help as I did a little bit of diagnostics there when this new driver/module was still in place.
Thanks
=======================================
========== /var/log/vmkernel.log ==========
=======================================
2019-09-11T11:30:12.434Z cpu3:2097564)Loading module vmkusb_nic_fling ...
2019-09-11T11:30:12.435Z cpu3:2097564)Elf: 2101: module vmkusb_nic_fling has license VMware
2019-09-11T11:30:12.443Z cpu3:2097564)Device: 192: Registered driver 'vmkusb_nic_fling' from 17
2019-09-11T11:30:12.443Z cpu3:2097564)Mod: 4962: Initialization of vmkusb_nic_fling succeeded with module ID 17.
2019-09-11T11:30:12.443Z cpu3:2097564)vmkusb_nic_fling loaded successfully.
2019-09-11T11:30:12.446Z cpu1:2097563)VMK_PCI: 914: device 0000:00:14.0 pciBar 0 bus_addr 0x404ac00000 size 0x10000
2019-09-11T11:30:12.446Z cpu1:2097563)WARNING: xhci_pci_attach:208: xhci devid 0x9ded8086: Success
2019-09-11T11:30:12.446Z cpu1:2097563)DMA: 679: DMA Engine 'xhci0 dma' created using mapper 'DMANull'.
2019-09-11T11:30:12.446Z cpu1:2097563)VMK_PCI: 764: device 0000:00:14.0 allocated 1 MSI interrupt
2019-09-11T11:30:12.513Z cpu1:2097563)Device: 327: Found driver vmkusb_nic_fling for device 0x6807430485a97896
...
2019-09-11T11:30:19.734Z cpu3:2097220)NetqueueBal: 4967: vusb0: new netq module, reset logical space needed
2019-09-11T11:30:19.734Z cpu3:2097220)NetqueueBal: 4996: vusb0: plugins to call differs, reset logical space
2019-09-11T11:30:19.734Z cpu3:2097220)NetPort: 1580: disabled port 0x3000002
2019-09-11T11:30:19.734Z cpu5:2097745)NetSched: 654: vusb0-0-tx: worldID = 2097745 exits
2019-09-11T11:30:19.734Z cpu6:2097295)CpuSched: 699: user latency of 2097755 vmnic0-0-tx 0 changed by 2097295 NetSchedHelper -6
2019-09-11T11:30:19.734Z cpu3:2097220)Uplink: 11689: enabled port 0x3000002 with mac 00:e0:4c:68:2b:9a
2019-09-11T11:30:19.734Z cpu7:2097296)CpuSched: 699: user latency of 2097756 vusb0-0-tx 0 changed by 2097296 NetSchedHelper -6
2019-09-11T11:30:21.544Z cpu7:2097578)usbd_setup_device_desc:1987: getting device descriptor at addr 1 failed, USB_ERR_IOERROR
2019-09-11T11:30:21.566Z cpu7:2097578)uhub_reattach_port:874: could not allocate new device
Hello,
I have an issue with v1.2 driver (sep 27,2019), esxi 6.7 update 3 (build 14320388) on NUC7i5BNH with RTL8153 Gigabit Ethernet Adapter, it's not working properly:
[root@esxi7:~] vmware -vl
VMware ESXi 6.7.0 build-14320388
VMware ESXi 6.7.0 Update 3
[root@esxi7:~] localcli system module list | grep usb
vmkusb_nic_fling true true
vmkusb false false
[root@esxi7:~] lsusb
Bus 001 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter
Bus 001 Device 001: ID 0e0f:8003 VMware, Inc. Root Hub
[root@esxi7:~] esxcli network nic list
Name PCI Device Driver Admin Status Link Status Speed Duplex MAC Address MTU Description
------ ------------ ------ ------------ ----------- ----- ------ ----------------- ---- ------------------------------------------------
vmnic0 0000:00:1f.6 ne1000 Up Up 1000 Full 94:c6:91:14:78:44 1500 Intel Corporation Ethernet Connection (4) I219-V
vusb0 Pseudo uether Up Up 1000 Full 00:e0:4c:68:00:18 1500 Realtek USB 101001000 LAN
[root@esxi7:~] esxcli network nic list
Name PCI Device Driver Admin Status Link Status Speed Duplex MAC Address MTU Description
------ ------------ ------ ------------ ----------- ----- ------ ----------------- ---- ------------------------------------------------
vmnic0 0000:00:1f.6 ne1000 Up Up 1000 Full 94:c6:91:14:78:44 1500 Intel Corporation Ethernet Connection (4) I219-V
[root@esxi7:~] dmesg | grep usb
2019-10-01T17:59:10.841Z cpu0:2097152)VisorFSTar: 1856: net_usbn.v00 for 0xd500 bytes
2019-10-01T17:59:10.852Z cpu0:2097152)VisorFSTar: 1856: ohci_usb.v00 for 0xffc8 bytes
2019-10-01T17:59:10.879Z cpu0:2097152)VisorFSTar: 1856: uhci_usb.v00 for 0xfe50 bytes
2019-10-01T17:59:10.879Z cpu0:2097152)VisorFSTar: 1856: usb_stor.v00 for 0x288f0 bytes
2019-10-01T17:59:10.879Z cpu0:2097152)VisorFSTar: 1856: usbcore_.v00 for 0x4f948 bytes
2019-10-01T17:59:10.882Z cpu0:2097152)VisorFSTar: 1856: vmkusb_n.v00 for 0x1804f8 bytes
2019-10-01T17:59:10.885Z cpu0:2097152)VisorFSTar: 1856: vmkusb.v00 for 0xf5400 bytes
2019-10-01T17:59:14.569Z cpu1:2097546)Loading module vmkusb_nic_fling ...
2019-10-01T17:59:14.570Z cpu1:2097546)Elf: 2101: module vmkusb_nic_fling has license VMware
2019-10-01T17:59:14.579Z cpu1:2097546)Device: 192: Registered driver 'vmkusb_nic_fling' from 20
2019-10-01T17:59:14.579Z cpu1:2097546)Mod: 4962: Initialization of vmkusb_nic_fling succeeded with module ID 20.
2019-10-01T17:59:14.579Z cpu1:2097546)vmkusb_nic_fling loaded successfully.
2019-10-01T17:59:14.648Z cpu0:2097535)Device: 327: Found driver vmkusb_nic_fling for device 0x3ca743048884e4af
2019-10-01T17:59:15.786Z cpu3:2097500)Activating Jumpstart plugin usb.
2019-10-01T17:59:15.905Z cpu3:2097590)Loading module usb ...
2019-10-01T17:59:15.906Z cpu3:2097590)Elf: 2101: module usb has license GPL
2019-10-01T17:59:15.907Z cpu3:2097590)module heap vmklnx_usb: Initial heap size = 262144, max heap size = 13860864
2019-10-01T17:59:15.907Z cpu3:2097590)module heap vmklnx_usb: using memType 2
2019-10-01T17:59:15.907Z cpu3:2097590)module heap vmklnx_usb: creation succeeded. id = 0x43099aca8000
2019-10-01T17:59:15.907Z cpu3:2097590)<6>usbcore: registered new interface driver usbfs
2019-10-01T17:59:15.907Z cpu3:2097590)WARNING: CharDriver: 356: Driver with name usbdevices is already using slot 48
2019-10-01T17:59:15.907Z cpu3:2097590)usbfs: failed to register usbdevices (-16)
2019-10-01T17:59:15.907Z cpu3:2097590)<6>usbcore: removing devices
2019-10-01T17:59:15.907Z cpu3:2097590)<6>usbcore: cleaning up devio
2019-10-01T17:59:15.907Z cpu3:2097590)<6>usbcore: degistering usbfs_driver
2019-10-01T17:59:15.907Z cpu3:2097590)<6>usbcore: deregistering interface driver usbfs
2019-10-01T17:59:15.907Z cpu3:2097590)<6>usbcore: cleaning up major
2019-10-01T17:59:15.907Z cpu3:2097590)<6>usbcore: unregistering notifier
2019-10-01T17:59:15.907Z cpu3:2097590)<6>usbcore: unregistering bus
2019-10-01T17:59:15.907Z cpu3:2097590)<6>usbcore: cleaning up debugfs
2019-10-01T17:59:15.907Z cpu3:2097590)<6>usbcore: Failed to initialize USB
2019-10-01T17:59:15.907Z cpu3:2097590)usb failed to load.
2019-10-01T17:59:15.907Z cpu3:2097590)WARNING: Elf: 3144: Kernel based module load of usb failed: Failure <Mod_LoadDone failed>
2019-10-01T17:59:15.911Z cpu3:2097500)Jumpstart plugin usb activation failed: usb->start() failed: exited with code 1
2019-10-01T17:59:18.068Z cpu2:2097560)usbd_setup_device_desc:1987: getting device descriptor at addr 2 failed, USB_ERR_IOERROR
2019-10-01T17:59:19.382Z cpu2:2097560)usbd_setup_device_desc:1987: getting device descriptor at addr 2 failed, USB_ERR_IOERROR
2019-10-01T17:59:21.204Z cpu3:2097560)usbd_setup_device_desc:1987: getting device descriptor at addr 2 failed, USB_ERR_IOERROR
2019-10-01T17:59:22.518Z cpu3:2097560)usbd_setup_device_desc:1987: getting device descriptor at addr 2 failed, USB_ERR_IOERROR
2019-10-01T17:59:24.335Z cpu3:2097560)usbd_setup_device_desc:1987: getting device descriptor at addr 2 failed, USB_ERR_IOERROR
2019-10-01T17:59:41.647Z cpu0:2098189)Starting service usbarbitrator
2019-10-01T17:59:41.647Z cpu0:2098189)Activating Jumpstart plugin usbarbitrator.
2019-10-01T17:59:42.257Z cpu3:2098189)Jumpstart plugin usbarbitrator activated.
2019-10-01T18:08:45.679Z cpu1:2097560)cdce_attach: usbd_transfer_setup success with alt 1
2019-10-01T18:08:45.680Z cpu2:2097569)Uplink: 11671: Device vusb0 not yet opened
2019-10-01T18:08:45.680Z cpu2:2097569)DMA: 679: DMA Engine 'vusb0-dma-engine' created using mapper 'DMANull'.
2019-10-01T18:08:45.680Z cpu2:2097569)Uplink: 13962: Opening device vusb0
2019-10-01T18:08:45.680Z cpu3:2097208)Uplink: 13811: Detected pseudo-NIC for 'vusb0'
2019-10-01T18:08:45.680Z cpu3:2097275)CpuSched: 699: user latency of 2099772 vusb0-0-tx 0 changed by 2097275 NetSchedHelper -6
2019-10-01T18:08:55.463Z cpu1:2097208)NetqueueBal: 4967: vusb0: new netq module, reset logical space needed
2019-10-01T18:08:55.463Z cpu1:2097208)NetqueueBal: 4996: vusb0: plugins to call differs, reset logical space
2019-10-01T18:08:55.463Z cpu1:2097208)NetqueueBal: 5032: vusb0: device Up notification, reset logical space needed
2019-10-01T18:08:55.463Z cpu0:2099772)NetSched: 654: vusb0-0-tx: worldID = 2099772 exits
2019-10-01T18:08:55.464Z cpu1:2097276)CpuSched: 699: user latency of 2099785 vusb0-0-tx 0 changed by 2097276 NetSchedHelper -6
2019-10-01T18:10:13.064Z cpu1:2097560)DMA: 724: DMA Engine 'vusb0-dma-engine' destroyed.
2019-10-01T18:10:13.064Z cpu2:2099785)NetSched: 654: vusb0-0-tx: worldID = 2099785 exits
2019-10-01T18:10:13.064Z cpu0:2097560)WARNING: usb_proc_free:249: failed to destroy world 2099770: Not found
2019-10-01T18:14:25.831Z cpu0:2097560)cdce_attach: usbd_transfer_setup success with alt 1
2019-10-01T18:14:25.832Z cpu2:2097569)DMA: 679: DMA Engine 'vusb0-dma-engine' created using mapper 'DMANull'.
2019-10-01T18:14:25.832Z cpu2:2097569)Uplink: 13962: Opening device vusb0
2019-10-01T18:14:25.832Z cpu1:2097208)Uplink: 13811: Detected pseudo-NIC for 'vusb0'
2019-10-01T18:14:25.832Z cpu3:2097276)CpuSched: 699: user latency of 2099849 vusb0-0-tx 0 changed by 2097276 NetSchedHelper -6
2019-10-01T18:14:35.470Z cpu2:2097208)NetqueueBal: 4967: vusb0: new netq module, reset logical space needed
2019-10-01T18:14:35.470Z cpu2:2097208)NetqueueBal: 4996: vusb0: plugins to call differs, reset logical space
2019-10-01T18:14:35.470Z cpu2:2097208)NetqueueBal: 5032: vusb0: device Up notification, reset logical space needed
2019-10-01T18:14:35.470Z cpu2:2099849)NetSched: 654: vusb0-0-tx: worldID = 2099849 exits
2019-10-01T18:14:35.471Z cpu3:2097276)CpuSched: 699: user latency of 2099858 vusb0-0-tx 0 changed by 2097276 NetSchedHelper -6
2019-10-01T18:15:27.285Z cpu0:2097560)DMA: 724: DMA Engine 'vusb0-dma-engine' destroyed.
2019-10-01T18:15:27.285Z cpu3:2099858)NetSched: 654: vusb0-0-tx: worldID = 2099858 exits
2019-10-01T18:15:27.285Z cpu3:2097560)WARNING: usb_proc_free:249: failed to destroy world 2099847: Not found
[root@esxi7:~] lsusb -v
Bus 001 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 3.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 9
idVendor 0x0bda Realtek Semiconductor Corp.
idProduct 0x8153 RTL8153 Gigabit Ethernet Adapter
bcdDevice 30.00
iManufacturer 1 Realtek
iProduct 2 USB 10/100/1000 LAN
iSerial 6 000001
bNumConfigurations 2
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 57
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 288mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 3
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 3
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0002 1x 2 bytes
bInterval 8
bMaxBurst 0
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 98
bNumInterfaces 2
bConfigurationValue 2
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 288mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 2 Communications
bInterfaceSubClass 6 Ethernet Networking
bInterfaceProtocol 0
iInterface 5 CDC Communications Control
CDC Header:
bcdCDC 1.10
CDC Union:
bMasterInterface 0
bSlaveInterface 1
CDC Ethernet:
iMacAddress 3 00E04C680018
bmEthernetStatistics 0x00000000
wMaxSegmentSize 1514
wNumberMCFilters 0x0000
bNumberPowerFilters 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 8
bMaxBurst 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 4 Ethernet Data
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 3
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 3
Binary Object Store Descriptor:
bLength 5
bDescriptorType 15
wTotalLength 22
bNumDeviceCaps 2
USB 2.0 Extension Device Capability:
bLength 7
bDescriptorType 16
bDevCapabilityType 2
bmAttributes 0x00000002
Link Power Management (LPM) Supported
SuperSpeed USB Device Capability:
bLength 10
bDescriptorType 16
bDevCapabilityType 3
bmAttributes 0x02
Latency Tolerance Messages (LTM) Supported
wSpeedsSupported 0x000e
Device can operate at Full Speed (12Mbps)
Device can operate at High Speed (480Mbps)
Device can operate at SuperSpeed (5Gbps)
bFunctionalitySupport 2
Lowest fully-functional device speed is High Speed (480Mbps)
bU1DevExitLat 10 micro seconds
bU2DevExitLat 2047 micro seconds
Device Status: 0x0000
(Bus Powered)