With the release of vSphere 8.0 Update 3 now generally available (release notes and direct download links below):
- ESXi
- vCenter
I know the first question I will get (which I already have already :P) is what about updated versions of the Nested ESXi Virtual Appliance and USB Network Native Driver for ESXi? 😅
You can find the newest versions of the Nested ESXi Virtual Appliance (8.0 Update 3) and the USB Network Native Driver for ESXi (1.15) on the VMware Flings Community (login is required), enjoy! 🥳
UPDATE (08/08/24) - The updated version 76444229 of the USB Network Native Driver for ESXi 8.0 Update 3 is now available, please download and use this version for anyone running into PSOD issues that were reported earlier.
The latest USB NIC fling appears to be broken with the new ESXi release on my setup, tried manually setting NIC speed but it still shows up as disconnected. How should I attempt to troubleshoot the issue?
Rolled back to U2d and everything was working fine again.
Can you provide a vm-support bundle and what type of USB NIC (VID/DID) would be great?
Same here. Upgraded to 8.0U3 with the network native driver fling version 75399077 and ESXi now shows the previously working (under 8.0U2b w/fling version 67561870) QNAP/Marvell/Aquantia 5Gb USB NIC link down host-side. Switch-side, it shows up at the correct speed, so it's only ESXi that's confused about link state. VID/DID 1c04:0015.
Is the USB primary or secondary? I tried one of the USB brands mentioned and wasn’t able to reproduce it locally but Engr has looked at bundles and see some oddness indeed
It's mapped to an uplink of a vDS. In each port group, this uplink is the first standby uplink.
Can you please try installing this debug version of the Fling, it has some changes to see if it can workaround the observed issues as well as additional logging.
https://higherlogicdownload.s3.amazonaws.com/BROADCOM/092f2b51-ca4c-4dca-abc0-070f25ade760/UploadedImages/Flings_Content/VMW_bootbank_vmkusb-nic-fling_1_14-2vmw_803_0_0_76444229.vib
Since this is just a debug version it is not signed, so you will need to install using --no-sig-check (e.g. esxcli software vib install -v /VMW_bootbank_vmkusb-nic-fling_1_14-2vmw_803_0_0_76444229.vib ---no-sig-check)
If it resolves the issue great, if not, please provide another vm-support bundle
Doesn't seem to be heeding the --no-sig-check option:
[root@esxi-nuc8:~] esxcli software vib update -f --no-sig-check --viburl=https://higherlogicdownload.s3.amazonaws.com/BROADCOM/092f2b51-ca4c-4dca-abc0-070f25ade760/UploadedImages/Flings_Content/VMW_bootbank_vmkusb-nic-fling_1_14-2vmw_803_
0_0_76444229.vib --dry-run
Installation Result
Message: Dryrun only, host not changed. The following installers will be applied: [BootBankInstaller]
VIBs Installed: VMW_bootbank_vmkusb-nic-fling_1.14-2vmw.803.0.0.76444229
VIBs Removed: VMW_bootbank_vmkusb-nic-fling_1.14-1vmw.803.0.0.75399077
VIBs Skipped:
Reboot Required: true
DPU Results:
[root@esxi-nuc8:~] esxcli software vib update -f --no-sig-check --viburl=https://higherlogicdownload.s3.amazonaws.com/BROADCOM/092f2b51-ca4c-4dca-abc0-070f25ade760/UploadedImages/Flings_Content/VMW_bootbank_vmkusb-nic-fling_1_14-2vmw_803_
0_0_76444229.vib
[InstallationError]
('VMW_bootbank_vmkusb-nic-fling_1.14-2vmw.803.0.0.76444229', 'Could not find a trusted signer: self-signed certificate')
cause = ('VMW_bootbank_vmkusb-nic-fling_1.14-2vmw.803.0.0.76444229', 'Could not find a trusted signer: self-signed certificate')
vibs = ['VMW_bootbank_vmkusb-nic-fling_1.14-2vmw.803.0.0.76444229']
Please refer to the log file for more details.
You need to download it and upload to ESXi datastore, you can’t patch using S3 URLs
yeah, i had tried that first but same result:
[root@esxi-nuc8:~] esxcli software vib update -f --no-sig-check -v /vmfs/volumes/60b24ffb-4e667eba-f6be-94c691ac3fe7/VIB/VM
W_bootbank_vmkusb-nic-fling_1_14-2vmw_803_0_0_76444229.vib
[InstallationError]
('VMW_bootbank_vmkusb-nic-fling_1.14-2vmw.803.0.0.76444229', 'Could not find a trusted signer: self-signed certificate')
cause = ('VMW_bootbank_vmkusb-nic-fling_1.14-2vmw.803.0.0.76444229', 'Could not find a trusted signer: self-signed certificate')
vibs = ['VMW_bootbank_vmkusb-nic-fling_1.14-2vmw.803.0.0.76444229']
Please refer to the log file for more details.
You don't need "-f" and you're using "update", you need to do "install"
Try following:
esxcli software vib install -v /vmfs/volumes/60b24ffb-4e667eba-f6be-94c691ac3fe7/VIB/VMW_bootbank_vmkusb-nic-fling_1_14-2vmw_803_0_0_76444229.vib --no-sig-check
same result:
[root@esxi-nuc8:~] esxcli software vib install -v /vmfs/volumes/60b24ffb-4e667eba-f6be-94c691ac3fe7/VIB/VMW_bootbank_vmkusb-nic-fling_1_14-2vmw_803_0_0_76444229.vib --no-sig-check
[InstallationError]
('VMW_bootbank_vmkusb-nic-fling_1.14-2vmw.803.0.0.76444229', 'Could not find a trusted signer: self-signed certificate')
cause = ('VMW_bootbank_vmkusb-nic-fling_1.14-2vmw.803.0.0.76444229', 'Could not find a trusted signer: self-signed certificate')
vibs = ['VMW_bootbank_vmkusb-nic-fling_1.14-2vmw.803.0.0.76444229']
Please refer to the log file for more details.
hm, that's very strange ... ESXi 8.0U3 is installed, correct?
Can you also confirm md5sum is good on download:
542d62f9475994511943b69822fae760 VMW_bootbank_vmkusb-nic-fling_1.14-2vmw.803.0.0.76444229.vib
yepo:
[root@esxi-nuc8:~] uname -a
VMkernel esxi-nuc8.[--------].com 8.0.3 #1 SMP Release build-24022510 Jun 11 2024 05:59:34 x86_64 x86_64 x86_64 ESXi
[root@esxi-nuc8:~] md5sum /vmfs/volumes/60b24ffb-4e667eba-f6be-94c691ac3fe7/VIB/VMW_bootbank_vmkusb-nic-fling_1_14-2vmw_803
_0_0_76444229.vib
542d62f9475994511943b69822fae760 /vmfs/volumes/60b24ffb-4e667eba-f6be-94c691ac3fe7/VIB/VMW_bootbank_vmkusb-nic-fling_1_14-2vmw_803_0_0_76444229.vib
The problem with the failing certificate check lies in the acceptance level. It is necessary to change to Communitysupported.
Thanks, Bernhard--that did the trick. (Had to first disable secure boot on the host, since without it ESXi didn't want to drop to CommunitySupported level.)
William: It might be of interest to you that VIB install worked just fine with --viburl citing the https link you provided directly. No local datastore needed.
In an unexpected twist, the new version _didn't_ solve the problem for me, despite others here having success with it. (It's definitely running the new version post-reboot. And the link continues to be up as reported by the switch and adapter LEDs, just not ESXi.)
ah yes, I assumed folks were aware that the default acceptance level would need to be changed in addition to ignoring the sig check ...
Can you provide a support bundle? I've had a few others also confirm their issues have been resolved with the debug version of the driver, so I'm wondering if this is something different ... the debug driver does have additional logging, so would be good to see if there's more info for Engineering
version 76444229 has same issue. switch shows port negotiated at 5Gb; esxi shows link down. again this is for usb NIC with VID/DID 1c04:0015 acting as a secondary priority uplink on a vds (where the primary priority uplink is not assigned any physical adapter). i guess i'll back the host out of vcenter and vds, do a clean install of 8.0U2b. 🙁
yeah, this aquantia/marvell 5gb one just won't show a link in 8.0U3 with any of the fling versions. even clean install in a standard switch as a solo uplink. others here seem to have success with the debug or new version on realtek 2.5gb chipsets. perhaps i'll pick up one of those for cheap or just stay on 8.0U2b for the 5gb.
Incidentally, 2.5Gb adapter with RTL8156B chipset works just fine. Maybe some future version will again support the Aquantia 5Gb chipsets like the 8.0U2 fling did.
well this is interesting... the Aquantia 5Gb _is_ actually "working" with fling version 76444229. vcenter and the esxi host UI just do their best to imply otherwise. both UIs show the "actual speed" aka "link speed" as "down" aka "link down." and both UIs dvs diagram show the little red 'x' or an empty (not green) port. but when i push traffic, it shows up on the vusb nic associated with this 'down' link (same on the switch side). 'thought perhaps the fling under 8.0U3 just doesn't correctly know how to deal with displaying 5Gb, but even forcing the switch port to 1Gb doesn't improve the display vmware-side.
Same here.
USB NICs appear as down on 8.0 Update 3 with latest USB fling from the flings page (ESXi80U3-VMKUSB-NIC-FLING-75399077-component-24052746), reportedly as 1.1.4
Rolling back to 8.0 Update 2 restored functionality.
I'm using 3x Cable Matters USB-A to 1GbE Adapter (CMI USB 101001000 LAN reported on the SSH console)
Can you provide support bundle post-upgrade?
I've upgraded it again to create the support bundle. Same issue
Support bundle: https://drive.google.com/file/d/1DA9508mLOyDfytEYh5keDkUddilMnuDG/view?usp=sharing
Can you please try installing this debug version of the Fling, it has some changes to see if it can workaround the observed issues as well as additional logging.
https://higherlogicdownload.s3.amazonaws.com/BROADCOM/092f2b51-ca4c-4dca-abc0-070f25ade760/UploadedImages/Flings_Content/VMW_bootbank_vmkusb-nic-fling_1_14-2vmw_803_0_0_76444229.vib
Since this is just a debug version it is not signed, so you will need to install using --no-sig-check (e.g. esxcli software vib install -v /VMW_bootbank_vmkusb-nic-fling_1_14-2vmw_803_0_0_76444229.vib ---no-sig-check)
If it resolves the issue great, if not, please provide another vm-support bundle
First, thanks so much for all the information and software you have provided. It is invaluable to me!
I have a Belkin F2CU040 on an Intel NUC 12 (https://www.belkin.com/usb-c-to-gigabit-ethernet-adapter/F2CU040btBLK.html) and am seeing the same issue.
Do you need additional support bundles?
Can you please try installing this debug version of the Fling, it has some changes to see if it can workaround the observed issues as well as additional logging.
https://higherlogicdownload.s3.amazonaws.com/BROADCOM/092f2b51-ca4c-4dca-abc0-070f25ade760/UploadedImages/Flings_Content/VMW_bootbank_vmkusb-nic-fling_1_14-2vmw_803_0_0_76444229.vib
Since this is just a debug version it is not signed, so you will need to install using --no-sig-check (e.g. esxcli software vib install -v /VMW_bootbank_vmkusb-nic-fling_1_14-2vmw_803_0_0_76444229.vib ---no-sig-check)
If it resolves the issue great, if not, please provide another vm-support bundle
Hello, I'm seeing similar issues since upgrade. It behaves like it's going up and down every second. Ping say's it's about 60% packet loss.
Network connectivity restored on virtual switch "vSwitch0", portgroups: "vspg-01g-v0101-vmk". Physical NIC vusb0 is up. Wednesday, June 26, 2024, 19:46:00 +0200
Lost network connectivity on virtual switch "vSwitch0". Physical NIC vusb0 is down. Affected portgroups:"vspg-01g-v0101-vmk". Wednesday, June 26, 2024, 19:45:59 +0200
Network connectivity restored on virtual switch "vSwitch0", portgroups: "vspg-01g-v0101-vmk". Physical NIC vusb0 is up. Wednesday, June 26, 2024, 19:45:58 +0200
Lost network connectivity on virtual switch "vSwitch0". Physical NIC vusb0 is down. Affected portgroups:"vspg-01g-v0101-vmk". Wednesday, June 26, 2024, 19:45:57 +0200
Network connectivity restored on virtual switch "vSwitch0", portgroups: "vspg-01g-v0101-vmk". Physical NIC vusb0 is up. Wednesday, June 26, 2024, 19:45:56 +0200
Lost network connectivity on virtual switch "vSwitch0". Physical NIC vusb0 is down. Affected portgroups:"vspg-01g-v0101-vmk". Wednesday, June 26, 2024, 19:45:55 +0200
Network connectivity restored on virtual switch "vSwitch0", portgroups: "vspg-01g-v0101-vmk". Physical NIC vusb0 is up. Wednesday, June 26, 2024, 19:45:54 +0200
Lost network connectivity on virtual switch "vSwitch0". Physical NIC vusb0 is down. Affected portgroups:"vspg-01g-v0101-vmk". Wednesday, June 26, 2024, 19:45:53 +0200
Network connectivity restored on virtual switch "vSwitch0", portgroups: "vspg-01g-v0101-vmk". Physical NIC vusb0 is up. Wednesday, June 26, 2024, 19:45:52 +0200
Lost network connectivity on virtual switch "vSwitch0". Physical NIC vusb0 is down. Affected portgroups:"vspg-01g-v0101-vmk". Wednesday, June 26, 2024, 19:45:51 +0200
Support bundle: https://drive.google.com/file/d/1B5f21QNdBcJBS_tSjvc-KxsQFhDFih3o/view?usp=sharing
Can you please try installing this debug version of the Fling, it has some changes to see if it can workaround the observed issues as well as additional logging.
https://higherlogicdownload.s3.amazonaws.com/BROADCOM/092f2b51-ca4c-4dca-abc0-070f25ade760/UploadedImages/Flings_Content/VMW_bootbank_vmkusb-nic-fling_1_14-2vmw_803_0_0_76444229.vib
Since this is just a debug version it is not signed, so you will need to install using --no-sig-check (e.g. esxcli software vib install -v /VMW_bootbank_vmkusb-nic-fling_1_14-2vmw_803_0_0_76444229.vib ---no-sig-check)
If it resolves the issue great, if not, please provide another vm-support bundle
Good morning,
I'm sorry for late response, I was off last few days.
I upgraded again to 8u3 and then installed 'VMW_bootbank_vmkusb-nic-fling_1_14-2vmw_803_0_0_76444229.vib'.
Connection to host is stable now, no packet loss and no errors or warnings in event log.
Thank you very much for your help and for everything you do for community 🙂
Awesome, thanks for confirming!
Hey William. The link to the appliances on your nested virtualization page is wrong. It needs to have "flings", not "fling". Thanks!
Thanks, fixed!
Hey William,
I’m looking tpm 2.0
Support pc for my lab as my nuc and GMKtec doesn’t support tpm 2.0. Can you recommend a mini pc that does? Or point me in the right direction:). Thank you! Huge fan
See https://williamlam.com/2023/05/asus-pn64-e1-on-esxi.html
Anyone know if there are any issues with NUCs, specifically the NUC12WSHi5? I'm wondering if the update on the ESXi hosts for the big/little core PSoD will be a factor in those upgrade?
Hey William,
I had the same problem after updating to update 3 using the new driver that my 2.5GBE USB Nics were not working correctly and I had to rollback to update 2.
I just saw your new debug version of the driver and tried again updating to update 3 using the debug version and so far everything looks fine. Thank you for your awesome support! I will update my other hosts once a release version of the new driver is released. Just wanted to give you a quick feedback.
Thanks Lucas! Good to hear it’s working
Hey William,
Thank you so much for all the work you do on this, really appreciated. I too can confirm that the new debug version of the driver is working correctly for my home lab environment on update 3. Will this debug version replace the Flings one officially ?
Thanks for your help! Yes, the intention is to provide an updated version of the Fling, once we get a few additional confirmations as we've also had other unrelated problems, so just want to make sure before we re-release a new version. Thanks for everyone's patience
hey! the debug Fling USB seems to work on my side too (after an unnecessary fresh install because I not found this post before!) Any ETA for the official Fling update. thanks!
Thanks for the confirmation! No ETA on updated driver as we're still awaiting some other folks with some other issues to confirm before we re-publish a new version
I installed ESXi restored the network configuration for management network so I could use the USB as a NIC.
Uploaded this Fling, installed it and rebooted.
I do have the samme issue as when I don't use this fling, ESXi won't set my USB Ethernet as management network as default so I always need to change it manually.
Is this something that can be fixed?
(Using this while I'm waiting for my Broadcom pcie card)
Hi,
On my side, it's working after applying the VMW_bootbank_vmkusb-nic-fling_1_14-2vmw_803_0_0_76444229.vib and unplug and plug the adaptor.
Rgds
My USB NICs are showing 100Mbps and should show 1Gbps ...I've update my baseline image with the VMW_bootbank_vmkusb-nic-fling_1_14-2vmw_803_0_0_76444229.vib
How do I apply the new image to all HOSTs in the cluster, so the NIC shows 1Gbps
William,
Love your site. So much that I thought I would share some code I created. I figured it might help someone else move faster into the Nested world.
I know you are a PWSH guru. I like Ansible so that is what I used. 🙂
https://github.com/jimccann-rh/nested-ova-ansible
This is awesome! Thanks for sharing
Hi There
Just upgraded to ESXi version 8.0 U3b - 24280767
Any news on USB Flings for that version ??
Since upgrade to version 8.02 my USB flings haven´t worked at all.
Just saying "link down" on all USB adaptors
Any update is appreciated
There’s been updated 8.0U3 version, please use that as its resolves issue that was being observed and was released awhile back
Hello and thank you for your work.
I am encountering issues with my adapters: RTL8156B.
The installation of the driver ESXi80U3-VMKUSB-NIC-FLING-75399077-component-24052746 on ESXi 8.0U3 went smoothly.
However, the management of the two adapters remains very unstable, and I regularly lose all access to the ESXi when manipulating vUSB0 and vUSB1, despite having a dedicated network card for managing the ESXi on a different switch.
I tried adding code to /etc/rc.local.d/local.sh, but it didn’t change anything.
For example, when restarting the physical 2.5G switch, I systematically lose access to the ESXi.
I am forced to reboot the server manually via the power button.
Can you help me with this?
Thank you in advance.
Not sure what's the problem, but on my end this is what I get:
[root@localhost:~] esxcli software vib install -v https://higherlogicdownload.s3.amazonaws.com/BROADCOM/092f2b51-ca4c-4dca-abc0-070f25ade760/UploadedImages/Flings_Content/VMW_bootbank_vmkusb-nic-fling_1_14-2vmw
_803_0_0_76444229.vib --no-sig-check
[InstallationError]
('VMW_bootbank_vmkusb-nic-fling_1.14-2vmw.803.0.0.76444229', 'Could not find a trusted signer: self-signed certificate')
cause = ('VMW_bootbank_vmkusb-nic-fling_1.14-2vmw.803.0.0.76444229', 'Could not find a trusted signer: self-signed certificate')
vibs = ['VMW_bootbank_vmkusb-nic-fling_1.14-2vmw.803.0.0.76444229']
You can’t update this way because you need to download zip and extract the actual offline bundle 🙂
Got it! But still, even downloading the file and trying an offline installation:
esxcli software vib install -v /TEMP/VMW_bootbank_vmkusb-nic-fling_1_14-2vmw_803_0_0_76444229.vib --no-sig-check
[InstallationError]
('VMW_bootbank_vmkusb-nic-fling_1.14-2vmw.803.0.0.76444229', 'Could not find a trusted signer: self-signed certificate')
cause = ('VMW_bootbank_vmkusb-nic-fling_1.14-2vmw.803.0.0.76444229', 'Could not find a trusted signer: self-signed certificate')
vibs = ['VMW_bootbank_vmkusb-nic-fling_1.14-2vmw.803.0.0.76444229']
Please refer to the log file for more details.
Sorry, USB NIC is distributed as offline bundle (eg zip), you need to use correct command. Search online for installing offline bundle for syntax
Nevermind... Solved. I had to disable the TPM, disable SecureBoot, set esxcli software acceptance set --level=CommunitySupported, reboot and then I was able to install it.
I have 10GE QNAP USB-C Ethernet adapter which works fine with standard VMware installation without additional VIBs and Startech USB-C 1GE Ethernet which is not recognized by default.
As soon, as I installed ESXi803-VMKUSB-NIC-FLING-76444229-component-24179899.zip, Startech 1GE becomes available, but 10GE QNAP disappears.
Both of them were operational together before on 6.7.
I have 3 VIB in the system:
Name Version Vendor Acceptance Level Install Date Platforms
----------------------------- ------------------------------------ ------ ---------------- ------------ ---------
atlantic 1.0.3.0-13vmw.803.0.0.24022510 VMW VMwareCertified 2024-10-28 host
vmkusb-nic-fling 1.14-2vmw.803.0.0.76444229 VMW VMwareCertified 2024-10-28 host
vmkusb 0.1-22vmw.803.0.0.24022510 VMW VMwareCertified 2024-10-28 host
How resolve the conflict?
Update with hardware details:
1 - 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet
AKA Startech US1GC301AU "USB-C to Gigabit Network Adapter"
2 - 1d6a:80b1 Network controller Ethernet controller: Marvell Felicity Network Adapter
AKA QNAP QNAP-T310G1S with 3.1.121 firmware "Thunderbolt 3 to 10GbE adapter"
AKA Marvell AQtion AQC100
Is it possible to have them both in ESXi 8.0U3? #1 - works with vmkusb-nic-fling, #2 - disappears from PCI bus when vmkusb-nic-fling is installed
Can you provide support bundle
Also, no need to double post in two places 🙂
Sure. I have just sent 2 support bundles by e-mail.
Thank you!
Attempting to install the latest USB Fling Nic but get repeated errors, Not sure what I am doing wrong, and google fu has not let me to an answer. Hate to ask but have spent an afternoon trying to resolve. Log file seem to just replicate same information. Can anyone point me in the right direction?
esxcli software component apply -d /vmfs/volumes/65720253-1d26ffb4-8efe-001b214e958b/VmWareDrivers/ESXi803-VMKUSB-NIC-FLING-7644422
9-component-24179899.zip
[StatelessError]
The transaction is not supported: VIB VMW_bootbank_vmkusb-nic-fling_1.14-2vmw.803.0.0.76444229 cannot be live installed.
Please refer to the log file for more details.
[root@ESXI-One:/var/log]
The error seems to indicate that your ESXi is booting up stateless, is that the case?