If anybody is getting the
VERR_SUPDRV_COMPONENT_NOT_FOUND error when trying to start a VM in VirtualBox when trying to set up Host Interface networking, the error is occurring because VirtualBox can’t communicate with the
To fix this, simply load the
# modprobe vboxnetflt
Then, try starting the VM again. If it works, you know that the problem is that the
vboxnetfltmodule is not loading on startup.
If it didn’t work, make sure the module has been built. A little
# /etc/init.d/vboxdrv setupought to do the trick.
On most Linux systems, you can add an entry to
/etc/modprobe.conf to make the module load on startup. (On OpenRC-based Gentoo systems, you can add an entry to
/etc/conf.d/modulesto do it the Gentoo Way™.)