Failed to open/create the internal network 'HostInterfaceNetworking-wlan0' (you might need to modprobe vboxnetflt to make it accessible) (VERR_SUPDRV_COMPONENT_NOT_FOUND).问题解决

今天开机使用VirtualBox OSE ，突然发现如下的错误：

启动虚拟电脑 winxp 失败.

Failed to open/create the internal network 'HostInterfaceNetworking-wlan0' (you might need to modprobe vboxnetflt to make it accessible) (VERR_SUPDRV_COMPONENT_NOT_FOUND).

Please install the virtualbox-ose-dkms package and execute 'modprobe vboxdrv' as root (VERR_SUPDRV_COMPONENT_NOT_FOUND)

用Google搜得一个解决方法：

打开控制台，输入：modprobe vboxnetflt命令

然后再次使用VirtualBox OSE ,打开winxp虚拟机，OK！

原因：

该问题是由于在系统开机的时候，vboxnetflt模块没有正常加载造成的。

有时间的XDJM，看看这篇文章吧：

VERR_SUPDRV_COMPONENT_NOT_FOUND on VirtualBox

6 January 2009

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 vboxnetflt driver.

To fix this, simply load the vboxnetflt module:

  # 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™.)

来源：http://jeremy.visser.name/2009/01/06/verr_supdrv_component_not_found-on-virtualbox/