Comments on: VERR_SUPDRV_COMPONENT_NOT_FOUND on VirtualBox

By: Mat

Mat — Tue, 10 Aug 2010 19:28:07 +0000

This worked for me too but…

Gentoo 2.6.34-gentoo-r1
virtualbox-bin v3.2.8

I had to also change the bridging support from compile in kernel (as other instruction said it should be configured) to a module to make the solutions posted at the top to work for me.

Hope this helps someone, off to post this somewhere else.

By: Nick Elliott

Nick Elliott — Mon, 26 Jul 2010 08:27:59 +0000

None of the above worked for me.

- modprobe… resulted in a ‘FATAL: Error’ message
- insmode… resulted in an ‘insmod: error’ message

However recompiling the VirtualBox driver module did the trick, to do this run the following command as root:

/etc/init.d/vboxdrv setup

By: Jeremy

Jeremy — Sat, 27 Mar 2010 12:16:19 +0000

It’s quite likely that for rwilla and rashvar (above) that running depmod -ae would also fix the problem for you.

By: rashvar

rashvar — Sat, 27 Mar 2010 11:36:32 +0000

insmod /lib/modules/2.6.32.9-70.fc12.x86_64/extra/VirtualBox-OSE/vboxnetflt.ko
also solved my problem! Fantastic, thanks!

By: rwilla

rwilla — Wed, 24 Mar 2010 07:03:01 +0000

modprobe vboxnetflt didn’t work! but
insmod /lib/modules/2.6.32.9-70.fc12.x86_64/extra/VirtualBox-OSE/vboxnetflt.ko
works; and then start virtualbox again. put your kernel number….