The USB NIC Fling is NOT supported with 7.0 Update 2, a new version must be created
The blog post is in regards to other USB NICs which maybe detected w/o the USB Fling, usually CDC-based USB NICs and that's why it still has benefits even thought this USB NIC Fling isn't currently supported. Once it will, then the same benefit would apply :)
Right....well the article started off singing the praises of the USB Fling in the first paragraph then went into this workaround, so it appeared that you were using the fling in regards to this, but as you now state you are referring to OTHER usb nics that may be detected.
Thanks for the clarification - still waiting for u2 :)
Yes and also the USB NIC Fling (as mentioned in blog post) is what motivated for this enhancement itself in ESXi. We've got this on our backlog but Engr has been quite busy and we hope to have something soon, so stay tuned
I have reported a bug some time ago regarding one CPU core hitting 100% after a while.
Unplugging and plugging the qnap adapter back in resolves it for a certain time untill it gets back.
I have tried all USB ports and combinations, unfortunately I ended up deleting the fling and not being able to use the adapter. Do you have any idea?
Thanks for finding this issue, I reposed on the bug thread.
As crazy busy on other stuffs, sorry for the delay response.
Can you create a vm-support or live dump when you see high CPU using?
So we can fix it in next update.
Thanks,
Songtao
Thanks for the help! Would you please provide a download-able link with that? Thanks !
Sure, can I send it via email or something as it contains "sensitive" information?
Hello, I have been using ESXi on my Intel Nuc and had to move the management port off the onboard nic to a USB nic. It works but if I reboot the USB nic gets detached and I have to go into the console and enabled it.
I guess the USB nic isn't detected in time upon boot up?
How can I fix this?
If I run esxcfg-nics -l I see my NIcs:
vmnic0
vusb0
vusb1
Thanks
Please see https://flings.vmware.com/usb-network-native-driver-for-esxi#instructions and "Persisting NIC Bindings" section
Okay... I'm probably just dumb (normally a windows guy, cut me some slack) but *where* do I set the usbBusFullScanOnBootEnabled option... says its not a valid key for a kernel option. Is it in the actual bootloader flags? I tried that too and it doesn't seem to make a difference
Make sure you're using the latest version of the Fling where that new boot option is valid. See https://www.virtuallyghetto.com/2021/03/esxi-7-0-update-2-enhancement-for-usb-nic-only-installations.html for detailed instruction as this has also been ported to ESXi 7.0 Update 2 (in terms of the new ESXi kernel boot option)
Andre
A little confused, a few posts down says 7.ou2 is NOT supported with this fling, but then on this blog it says to do a workaround with 7.02 https://www.virtuallyghetto.com/2021/03/esxi-7-0-update-2-enhancement-for-usb-nic-only-installations.html
I've tried to upgrade my 7.0.u1 and it fails complaining about the dependencies as mentioned here earlier. How was this other person able to get this to work?