VirtualBox error if kernel module loader in /boot/loader.conf (WAS Re: Loading kernel modules for virtualbox via script)

[Leslie Jensen]

On 2009-12-22 23:17, Paul Wootton wrote:

> I too get an error on starting a VM if I try to load the modules from
> /boot/loader.conf. For me, the loading of vboxnetflt does not seem to
> work correctly. I dont load vboxnetadp, so I cant comment on that.
>
> /boot/loader.conf
> zfs_load="YES"
> vboxdrv_load="YES"
> vboxnetflt_load="YES"
>
>
> If I try to start a VM that is using the "Bridged Ethernet" adapter, the
> error I get is
>
> "Failed to start the virtual machine Win Vista
>
> Failed to open/create the internal network 'HostInterfaceNetworking-re0'
> (VERR_SUPDRV_COMPONENT_NOT_FOUND).
>
> Failed to attach the network LUN
> (VERR_SUPDRV_COMPONENT_NOT_FOUND).
>
> Unknown eror creating VM (VERR_SUPDRV_COMPONENT_NOT_FOUND).
>
> Details
> Result Code: NS_ERROR_FAILURE (0x80004005)
> Component: Console
> Interface: IConsole {0a51994b-cbc6-4686-94eb-d4e4023280e2}"
>
>
> I know the module got loaded.
> [paul at demophon /usr/home/paul]$ kldstat
> Id Refs Address Size Name
> 1 25 0xffffffff80100000 e7c540 kernel
> 2 1 0xffffffff80f7d000 18a788 zfs.ko
> 3 2 0xffffffff81108000 3778 opensolaris.ko
> 4 2 0xffffffff8110d000 41e88 vboxdrv.ko
> 5 1 0xffffffff8114f000 6960 vboxnetflt.ko
> 6 1 0xffffffff81223000 38fc linprocfs.ko
> 7 1 0xffffffff81227000 1bcc4 linux.ko
>
> If I then do a kldunload vboxnetflt followed by kldload vboxnetflt, I
> can now start and stop my VMs to my heart's content.
> Im using 9 CURRENT and I only started using /boot/loader.conf for the
> vbox modules about a month back. The vboxnetflt module has never worked
> correctly for me this way
>
> Paul

Thanks for starting the new tread :-)

This is exactly the same problem I'm having.

I'm on 8.0-RELEASE

/Les