WilliamLam.com

You are here: Home / Automation / Nested ESXi Virtual Appliance & USB Network Native Driver for ESXi for vSphere 8.0 Update 3

Nested ESXi Virtual Appliance & USB Network Native Driver for ESXi for vSphere 8.0 Update 3

by // 38 Comments

With the release of vSphere 8.0 Update 3 now generally available (release notes and direct download links below):

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! 🥳

More from my site

Comments

  1. 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.

    Reply

      • 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.

        Reply

        • 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

          Reply

          • 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

          Reply

          • 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.

          • 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

    • 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.

      Reply

  2. 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

    Reply

  3. Hey William. The link to the appliances on your nested virtualization page is wrong. It needs to have "flings", not "fling". Thanks!

    Reply

  4. 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

    Reply

  5. 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?

    Reply

  6. 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.

    Reply

  7. 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 ?

    Reply

    • 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

      Reply

  8. 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!

    Reply

    • 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

      Reply

Thanks for the comment!

This site uses Akismet to reduce spam. Learn how your comment data is processed.