Please provide your feedback in this short Flings' survey.
Nov 19, 2021

7.0U3 in its entirety has been pulled. So I'd avoid going there for now.

Nov 19, 2021


I have an EXSI with two adapters that I just upgraded.

Update of ESXi-7.0U2d-18538813 to ESXi-7.0U3b-18905247

This is done in the following ways:

1 - I have deleted the old version ESXi702-VMKUSB-NIC-FLING-47140841-component-18150468
2 - Reboot
3 - Installation of ESXi-7.0U3b-18905247
4 - Reboot
5 - Installation of ESXi703-VMKUSB-NIC-FLING-51233328-component-18902399
6 - Reboot

I do have the two adapters that are UP.

I work on Distributed Switch.

The only problem is that the vusb disengages from the Distributed Switch with the reboot of the ESXI.

I have to reconfigure them in VCenter.

Before the update no problem.

Does anyone have any ideas?

Thank you in advance.

Nov 17, 2021

Using AutoDeploy. Loaded VMware-ESXi-7.0U3b-18905247 and the latest USB fling.

Ran the ISO export and got this error:

An error occured while performing the task<br/>
(None, None, &#x27;Error retrieving file for VIB \&#x27;VMW_bootbank_vmkusb-nic-fling_1.8-3vmw.703.0.15.51233328\&#x27;: (&quot;&lt;_io.BufferedReader name=\&#x27;/storage/imagebuilder/vibs/VMW_bootbank_vmkusb-nic-fling_1.8-3vmw.703.0.15.51233328.vib\&#x27;&gt;&quot;, &quot;Error opening file object for VIB \&#x27;VMW_bootbank_vmkusb-nic-fling_1.8-3vmw.703.0.15.51233328\&#x27;: Expected value \&#x27;[]\&#x27; for attribute \&#x27;swplatforms\&#x27;, but found value \&#x27;[&lt;vmware.esximage.Vib.SoftwarePlatform object at 0x7fc3945f18d0&gt;]\&#x27;.&quot;); (&quot;&lt;zipfile.ZipExtFile name=\&#x27;vib20/vmkusb-nic-fling/VMW_bootbank_vmkusb-nic-fling_1.8-3vmw.703.0.15.51233328.vib\&#x27; mode=\&#x27;r\&#x27; compress_type=deflate&gt;&quot;, &quot;Error opening file object for VIB \&#x27;VMW_bootbank_vmkusb-nic-fling_1.8-3vmw.703.0.15.51233328\&#x27;: Expected value \&#x27;[]\&#x27; for attribute \&#x27;swplatforms\&#x27;, but found value \&#x27;[&lt;vmware.esximage.Vib.SoftwarePlatform object at 0x7fc3945f1c90&gt;]\&#x27;.&quot;).&#x27;)

I suspect this latest USB driver is incompatible.. Any ideas?

Nov 18, 2021

Additional Update: Using VMware PowerCLI we get a little more descriptive on the issue.

PS D:\esx> Export-EsxImageProfile -ImageProfile esxcustom .\esxcustom.iso -ExportToIso -Force
WARNING: The image profile fails validation. The ISO / Offline Bundle will still be generated but may contain errors and may not boot or be functional. Errors:
WARNING: VIB VMW_bootbank_vmkusb-nic-fling_1.8-3vmw.703.0.15.51233328 requires vmkapi_incompat_2_9_0_0, but the requirement cannot be satisfied within the ImageProfile.
WARNING: VIB VMW_bootbank_vmkusb-nic-fling_1.8-3vmw.703.0.15.51233328 requires vmkapi_2_9_0_0, but the requirement cannot be satisfied within the ImageProfile.

Nov 15, 2021

Ever since I followed these steps on my NUC10i7FNH (with the onboard ethernet as management NIC and a single UGREEN AX88179 USB NIC attached):

- while running ESXi 7.0 U2d, uninstalled, and reboot
- updated to 7.0 U3a, and reboot
- installed, and reboot

My vswitch that uses the USB NIC now shows no uplink/physical adapter after a reboot. The USB NIC appears to be enabled in the GUI, and when I edit the vswitch, it shows the uplink, but when I boot up a VM on that vswitch, it definitely gets no network. I have to edit the vswitch, delete the uplink, save it, then add the uplink back in, save it, and it works only until the next reboot. Updated to 7.0 U3b and still seeing the same issue. Everything worked great with 7.0 U2d with the USB NIC persisting just fine through reboots.

Anyone seeing the same or have any ideas?

Nov 18, 2021

I experienced the same issue. My solution is a bit nasty, I added the following commands after esxcfg-vswitch -R.

sleep 2
esxcli network nic down -n vusb0
sleep 2
esxcli network nic up -n vusb0

Maybe it will work for your setup as well.