Kernel module for virtualbox-ose missing

[Wouter Stomp]

Binary package hint: virtualbox
After installing virtualbox, when I try to start a virtual machine, I get the following error:

VirtualBox kernel driver not installed. The vboxdrv kernel module was either not loaded or /dev/vboxdrv was not created for some reason. Re-setup the kernel module by executing '/etc/init.d/vboxdrv setup' as root.
VBox status code: -1908 (VERR_VM_DRIVER_NOT_INSTALLED).

Result Code:
0x80004005
Component:
Console
Interface:
IConsole {1dea5c4b-0753-4193-b909-22330f64ec45}

We have this error because vboxdrv module is not installed.

[Chuck Short (zulcss)]

Im guessing the kernel module is not installed which version of ubuntu are you using?

[Wouter Stomp (wouterstomp-deactivatedaccount)]

Gutsy (virtualbox is only in the gutsy repository)

[Patrice Vetsel (vetsel-patrice)]

virtualbox-source have to be installed too. After that you have to read the README in /usr/share/doc/virtualbox-source to finish compilation/installation of the virtualbox module.

Thank for your report.

[Wouter Stomp (wouterstomp-deactivatedaccount)]

If virtualbox-source needs to be installed too, the virtualbox package should depend on it rather than recommend it like now. And there should be a better error message for this.

If you install the package from the virtualbox website, compilation/installation of the module is done automatically during installation. Could this also be done for the ubuntu package?

[Steve Kowalik (stevenk)]

virtualbox-source does not have to be installed, since that is the source of the modules, not the modules themselves. I am going to create a separate package that has the modules for every kernel, but it will take me a little while to sort out.

[viking777 (viking-f2s)]

I can confirm this error with virtualbox. I have both the virtualbox-ose and virtualbox-source-ose packages installed and I still get the same error. The installation instructions in /usr/share/doc make no difference to this situation, I have carried them out but I still get the VM-DRIVER-NOT-INSTALLED message. The command /etc/init.d/vboxdrv does not exist and neither does /dev/vboxdrv.

X86-64 Kubuntu Gutsy Intel dual core laptop.

[Steve Kowalik (stevenk)]

As I said before, virtualbox-ose-source isn't required to be installed. That package only installs the source code for the Virtualbox modules - not the modules themselves.

I am going to sort out a way to a get the modules shipped for i386 and amd64 kernels, and I will update this bug report with more news when it comes about.

[Wouter Stomp (wouterstomp-deactivatedaccount)]

Why not provide the unmodified upstream package which compiles the kernel modules itself for the installed kernel?

[Steve Kowalik (stevenk)]

Why force every user that installs virtualbox to have the kernel headers and a development environment installed? That then also puts files under /lib/modules/<kernel version> that aren't under dpkg's control, which defeats among other things, update-initramfs, since you remove the old kernel, but the virtualbox modules are still there, which means dpkg won't remove the directory, and update-initramfs says "Ah, I need to regenerate the initramfs for every directory under /lib/modules". Which now includes the old kernel, since dpkg didn't delete the directory. This leads to user confusion as well, since update-initramfs will say that it is updating the initramfs for that old kernel which the user has just removed.

[Hani Nabil Boustani (boustanihani)]

I just wan't to say I can confirm this bug on Kubuntu Gusty :)

[CheolHan Yoon (mait)]

I'v got the same problem. Hope to just can run virtualbox with 'sudo apt-get install virutalbox'

[ovizii (ovizii)]

same problem here. I found out a modprobe vboxdrv fixes this and I can start virtualbox, but after a reboot same problem again :-(

[Mike MacCana (lovekudu)]

Same here. It seems kernel 2.6.22-12-generic does not yet include the missing drivers.

[dodgy_pro (dodgy-pro-deactivatedaccount)]

We are all looking forward to having Virtualbox work easily enough under Gutsy. I can understand that it takes some time till the fix release.

[Daniel Gonzalez (gonvaled)]

Adding the following software source:
http://www.virtualbox.org/debian feisty non-free

and selecting the package virtualbox (1.5.0-24069-1_Ubuntu_feisty) works.

I am using Gutsy, updated to the current release.

I get a complain about non signed package, though. If I ignore it, everything works.

[Conrad Knauer (atheoi)]

Daniel Gonzalez: The innotek GmbH archive signing key is 927CCC73. Run the following command from Terminal to add it:

gpg --keyserver subkeys.pgp.net --recv 927CCC73 && gpg --export --armor 927CCC73 | sudo apt-key add -

enter your password when prompted.

[Zachary Waldowski (zwaldowski)]

So, what needs to be done is either have the vboxdrv compiled into the kernel, or have a "virtualbox-ose-modules" package, right?

[Moritz Reiter (schallstrom)]

@Daniel Gonzales

When you install VirtualBox from the innotek repos, you are not using the Open Source Edition anymore, but the commercial edition which is closed source, free for personal use.

It would be great if the vboxdrv module would be installable through a "virtualbox-ose-modules" package or something like this.

[finss (finss)]

I confirm the bug for the 2.6.22-14-generic kernel from gutsy. There's only virtualbox-ose-modules-2.6.22-13-generic and virtualbox-ose-modules-2.6.22-13-server on the repositery. So I wait they're comming..

[Daniel Hahler (blueyed)]

I'm closing this as "Fix released", not that we have virtualbox-ose-modules.

[Daniel Hahler (blueyed)]

Sorry, I've meant to say:
I'm closing this as "Fix released", _now_ that we have virtualbox-ose-modules.

[William F Pearson (wfpearson)]

Thanks, good with me.

On 10/13/07, dAniel hAhler <email address hidden> wrote:
> I'm closing this as "Fix released", not that we have virtualbox-ose-
> modules.
>
> ** Summary changed:
>
> - virtualbox should depend on virtualbox-source
> + Kernel module for virtualbox-ose missing
>
> ** Changed in: virtualbox-ose (Ubuntu)
> Status: Confirmed => Fix Released
>
> --
> Kernel module for virtualbox-ose missing
> https://bugs.launchpad.net/bugs/137599
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--
William F Pearson III

Government is not reason, it is not eloquence — it is force! Like
fire, it is a dangerous servant and a fearful master. [George
Washington]

[Moritz Reiter (schallstrom)]

Fix works for me. Thanks :)

[kripken (kripkenstein)]

I still experience this bug on Hardy, I get the "VirtualBox kernel driver not installed" error.

Following the error message's suggestion, "Please install the virtualbox-ose-modules package for your kernel, e.g. virtualbox-ose-modules-generic.", I installed that package, but no improvement. I tried a reboot and adding myself to the group vboxusers, still the same error.

[kripken (kripkenstein)]

Please ignore my previous comment for now, I think I may know what the problem is. Sorry for the bother.

[Daniel Hahler (blueyed)]

kripkenstein, if it has been fixed by a recent update for you, please confirm it in bug 226753.

[kripken (kripkenstein)]

Daniel: I forgot before that I was running the kernel from hardy-proposed (-17), and I think that's why virtualbox won't work for me. So my experience is probably not relevant for this bug.

[Pablo Angulo (pablo-angulo)]

This happened to me in intrepid ibex, both when I boot the current kernel (2.6.27), for which there is no virtualbox-ose-module package, but also when I boot with the 2.6.25-5-generic, for which there is the package named exactly "virtualbox-ose-modules-2.6.26-5-generic".

I'll try to compile with the sources and report later, but I think the package with the matching kernel name should work.

[Pablo Angulo (pablo-angulo)]

Atuo-compilation with virtualbox-ose-source failed. I attach error log.
The command issued was:

sudo module-assistant auto-install virtualbox-ose