On 04/27/2012 10:12 AM, Richard C. Steffens wrote:
> I got a notice of an update for VirtualBox this morning. I downloaded
> virtualbox-4.1_4.1.14-77440~Ubuntu~lucid_i386.deb and installed it. Now,
> when I try to start one of my virtual machines I get the following
> error message:
>
> ---------------------------------------------------------------------------------------
> Failed to open a session for the virtual machine Wirns.
>
> Failed to open/create the internal network
> 'HostInterfaceNetworking-eth0' (VERR_SUPDRV_COMPONENT_NOT_FOUND).
>
> One of the kernel modules was not successfully loaded. Make sure that no
> kernel modules from an older version of VirtualBox exist. Then try to
> recompile and reload the kernel modules by executing
> '/etc/init.d/vboxdrv setup' as root (VERR_SUPDRV_COMPONENT_NOT_FOUND).
>
> Result Code: NS_ERROR_FAILURE (0x80004005)
> Component: Console
> Interface: IConsole {1968b7d3-e3bf-4ceb-99e0-cb7c913317bb}
> ---------------------------------------------------------------------------------------
>
> This happened to me recently (a few days ago? a week or so?) and I
> solved it by "executing '/etc/init.d/vboxdrv setup' as root." Today,
> however, when I try that I get another error message:
>
> ---------------------------------------------------------------------------------------
> rsteff@moonguide:~$ sudo /etc/init.d/vboxdrv setup
> * Stopping VirtualBox kernel modules
> * Cannot unload module vboxdrv
> rsteff@moonguide:~$
> ---------------------------------------------------------------------------------------
>
> In the instructions above is, "Make sure that no kernel modules from an
> older version of VirtualBox exist." I understand very minimally what a
> kernel module is, but not how to recognize one, or where to look for a
> specific one. Is that what I need to do to fix this problem?
>
I thought I'd chase this down on the VirtualBox forums. It looks like
the entire VirtualBox site is down.
Rather than wait until Monday I fell back on the bad habit of rebooting
the machine. After booting I still got an error message about "executing
'/etc/init.d/vboxdrv setup' as root." This time it worked. Once finished
I started up VirtualBox and one of my virtual machines. It worked as
expected.
--
Regards,
Dick Steffens
_______________________________________________
PLUG mailing list
[email protected]
http://lists.pdxlinux.org/mailman/listinfo/plug
