Hi All, I didn't found a solution for now but in found the kinds of errors in the log /var/log/vmkwarning.log
If this can help to troubleshoot.
2024-12-17T20:15:54.666Z Wa(180) vmkwarning: cpu11:1049011)WARNING: vmkusb_nic_fling: udev 0x4316d29da348, endpoint 0x2: invalid state 5: Failure 2024-12-17T20:15:54.687Z Wa(180) vmkwarning: cpu9:1049010)WARNING: World: vm 1071973: 4362: vm not found 2024-12-17T20:15:54.687Z Wa(180) vmkwarning: cpu9:1049010)WARNING: vmkusb_nic_fling: failed to destroy world 1071973: Not found 2024-12-17T20:15:54.687Z Wa(180) vmkwarning: cpu11:1049011)WARNING: vmkusb_nic_fling: udev 0x4316d29da348, endpoint 0x0: invalid state 5: Failure 2024-12-17T20:15:55.486Z Wa(180) vmkwarning: cpu1:1048991)WARNING: Uplink: 13578: vusb0, Failed to acquire parent device ID, err: 0xbad0007 2024-12-17T20:16:04.183Z Wa(180) vmkwarning: cpu7:1049011)WARNING: vmkusb_nic_fling: udev 0x4316d29da348, endpoint 0x81: invalid state 5: Failure 2024-12-17T20:16:04.183Z Wa(180) vmkwarning: cpu7:1049011)WARNING: vmkusb_nic_fling: udev 0x4316d29da348, endpoint 0x0: invalid state 5: Failure 2024-12-17T20:16:04.183Z Wa(180) vmkwarning: cpu8:1049011)WARNING: vmkusb_nic_fling: udev 0x4316d29da348, endpoint 0x83: invalid state 5: Failure 2024-12-17T20:16:04.183Z Wa(180) vmkwarning: cpu8:1049011)WARNING: vmkusb_nic_fling: udev 0x4316d29da348, endpoint 0x2: invalid state 5: Failure 2024-12-17T20:16:04.206Z Wa(180) vmkwarning: cpu2:1049010)WARNING: World: vm 1071981: 4362: vm not found 2024-12-17T20:16:04.206Z Wa(180) vmkwarning: cpu2:1049010)WARNING: vmkusb_nic_fling: failed to destroy world 1071981: Not found 2024-12-17T20:16:05.004Z Wa(180) vmkwarning: cpu2:1048991)WARNING: Uplink: 13578: vusb0, Failed to acquire parent device ID, err: 0xbad0007 2024-12-17T20:16:19.966Z Wa(180) vmkwarning: cpu3:1049011)WARNING: vmkusb_nic_fling: udev 0x4316d29da348, endpoint 0x81: invalid state 5: Failure 2024-12-17T20:16:19.966Z Wa(180) vmkwarning: cpu3:1049011)WARNING: vmkusb_nic_fling: udev 0x4316d29da348, endpoint 0x83: invalid state 5: Failure 2024-12-17T20:16:19.966Z Wa(180) vmkwarning: cpu3:1049011)WARNING: vmkusb_nic_fling: udev 0x4316d29da348, endpoint 0x2: invalid state 5: Failure 2024-12-17T20:16:19.987Z Wa(180) vmkwarning: cpu6:1049010)WARNING: World: vm 1072053: 4362: vm not found 2024-12-17T20:16:19.987Z Wa(180) vmkwarning: cpu6:1049010)WARNING: vmkusb_nic_fling: failed to destroy world 1072053: Not found 2024-12-17T20:16:19.987Z Wa(180) vmkwarning: cpu6:1049011)WARNING: vmkusb_nic_fling: udev 0x4316d29da348, endpoint 0x0: invalid state 5: Failure 2024-12-17T20:16:20.798Z Wa(180) vmkwarning: cpu2:1048991)WARNING: Uplink: 13578: vusb0, Failed to acquire parent device ID, err: 0xbad0007 2024-12-17T20:16:34.099Z Wa(180) vmkwarning: cpu11:1049011)WARNING: vmkusb_nic_fling: udev 0x4316d29da348, endpoint 0x81: invalid state 5: Failure 2024-12-17T20:16:34.099Z Wa(180) vmkwarning: cpu11:1049011)WARNING: vmkusb_nic_fling: udev 0x4316d29da348, endpoint 0x83: invalid state 5: Failure 2024-12-17T20:16:34.099Z Wa(180) vmkwarning: cpu11:1049011)WARNING: vmkusb_nic_fling: udev 0x4316d29da348, endpoint 0x2: invalid state 5: Failure 2024-12-17T20:16:34.120Z Wa(180) vmkwarning: cpu4:1049010)WARNING: World: vm 1072101: 4362: vm not found 2024-12-17T20:16:34.120Z Wa(180) vmkwarning: cpu4:1049010)WARNING: vmkusb_nic_fling: failed to destroy world 1072101: Not found 2024-12-17T20:16:34.120Z Wa(180) vmkwarning: cpu11:1049011)WARNING: vmkusb_nic_fling: udev 0x4316d29da348, endpoint 0x0: invalid state 5: Failure 2024-12-17T20:16:34.920Z Wa(180) vmkwarning: cpu2:1048991)WARNING: Uplink: 13578: vusb0, Failed to acquire parent device ID, err: 0xbad0007 2024-12-17T20:16:44.190Z Wa(180) vmkwarning: cpu0:1049011)WARNING: vmkusb_nic_fling: udev 0x4316d29da348, endpoint 0x81: invalid state 5: Failure 2024-12-17T20:16:44.190Z Wa(180) vmkwarning: cpu0:1049011)WARNING: vmkusb_nic_fling: udev 0x4316d29da348, endpoint 0x83: invalid state 5: Failure 2024-12-17T20:16:44.212Z Wa(180) vmkwarning: cpu1:1049010)WARNING: World: vm 1072111: 4362: vm not found 2024-12-17T20:16:44.212Z Wa(180) vmkwarning: cpu1:1049010)WARNING: vmkusb_nic_fling: failed to destroy world 1072111: Not found 2024-12-17T20:16:44.212Z Wa(180) vmkwarning: cpu0:1049011)WARNING: vmkusb_nic_fling: udev 0x4316d29da348, endpoint 0x0: invalid state 5: Failure 2024-12-17T20:16:45.012Z Wa(180) vmkwarning: cpu6:1048991)WARNING: Uplink: 13578: vusb0, Failed to acquire parent device ID, err: 0xbad0007
Thank you @Takumi Takahata
So whilst I didn't have the disconnection issue (AFAIK) I did have the install issue.
Only fix for me was to remove the USB NIC fling, upgrade as normal, then add the USB Fling.
I'm not sure why VMware cant add it - even if it has warnings not for production use - as lets face it, no one in their right mind would use a removable USB NIC.....
Lets see what happens in the future
Any solution foundI have the same problem now
I'm also getting similar error when trying to upgrade. It fails using VUM in the vCenter GUI with an error:
An error occurred during host configuration exit status: 14
Nothing of note in the usual logs..... and then trying from CLI:
esxcli software profile update -p ESXi-8.0U3-24022510-standard -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml --no-hardware-warning [DependencyError] On platform embeddedEsx, VIB VMW_bootbank_vmkusb-nic-fling_1.12-1vmw.801.0.0.64098092 requires vmkapi_incompat_2_11_0_0, but the requirement cannot be satisfied within the ImageProfile.
Some extra background - also it is not possible to build a new 8.0U3 ISO with the current USB fling - below is error output which is similar to the earlier flings that were broken after 8.0U2"
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: On platform embeddedEsx, VIB VMW_bootbank_vmkusb-nic-fling_1.12-2vmw.802.0.0.67561870 requires vmkapi_incompat_2_12_0_0, but the requirement cannot be satisfied within the ImageProfile.