VirtualBox keeps failing even though ran "/etc/init.d/vboxdrv setup"!!

English Applications
1

I keep getting the error below even though I:

  1. Added myself to vboxusers
  2. Installed dkms
  3. Ran the “sudo /etc/init.d/vboxdrv setup” command.

When I run “/etc/init.d/vboxdrv setup” it gives me the error:

modprobe vboxdrv failed. Please use ‘dmesg’ to find out why

The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing

'/etc/init.d/vboxdrv setup'

as root. Users of Ubuntu, Fedora or Mandriva should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.

One other thing, I looked in the file system and there is no “/dev/vboxdrv”. Is this correct?

2

install the kernel sources and headers:

zypper in kernel-source kernel-devel kernel-desktop-devel kernel-default-devel

and try to recompile the vbox module:

 service vboxdrv setup
3

This is inside VirtualBox and for Ubuntu (my host is opensuse). Any idea how to download those sources for Ubuntu?

4

you may also look at the logs:

tail -f /var/log/vbox-install.log

5

apt-get install build-essential

6

This is outside VirtualBox ! You don’t have to do that inside your virtual machine.

7

Thanks. I think the problem might be because I’m using Guest Additions.

Also, I think maybe I’ve been unclear. Here’s my setup and issue:


* OpenSUSE 11.2
        * VirtualBox
                * Ubuntu 10.04
                        * VirtualBox (THIS is the one with the issue)
                                * WebOS (Never get this far)
8

Ok, so are you trying to create a virtual machine inside a virtual machine?

9

Why do you want a guest inside a guest? If it’s possible, I imagine there would be performance problems.

10

Because WebOS’s SDK only works inside Ubuntu Linux or Windows along with a virtual box for the webos emulator. Since I’m on OpenSUSE, I have no choice but to run it inside ubuntu guest.

11

This whole exercise seems unbelievable to me

WebOS needs what to run exactly?

12

As far as I know, the sources are/were available for Ubuntu and it’s easier to compile there. I did try a while ago and got it installed in a VM. But it was to buggy and practically useless. I understand that the OP wants to use Ubuntu for that purpose and I would recommand to install it rather on a separate partition and dual boot with openSUSE. That’s what I would do. That’s actually what I did. Although the VM in the VM in the VM sounds funny … like the infinite cat : The Infinite Cat Project - One Cat Watching Another - Plus Cat Comics, Pictures, Movies and Stories :slight_smile:

13

Oh ! WebOS ? I don’t know about that one. I was thinking about ‘Chrome OS’.

14

It’s novacom that causes the issue. This is required and does not work on openSUSE.

I have done virtualbox inside a guest OS before so I’m thinking the issue is guest additions. I’m going to try it in Ubuntu without guest additions and see if that works.

15

I have just faced the same problem with you but by just following your useful instruction i came up with the problem!!:wink:

Let me make a notice about the commands (i use openSUSE 11.4)

The totally steps are :

Step 1 :

Install the kernerl sources and headers :

zypper in kernel-source kernel-devel kernel-desktop-devel kernel-default-devel

Step 2 :

Install the gcc compiler so as to compile the module!

sudo zypper in gcc

**Step 3 : **

Install the appropiate service:

sudo /sbin/service vboxdrv setup

My first post in openSUSE Forum. I hope that users who may face the same problem will be able to solve it!

16

On 04/26/2011 04:36 PM, zoumpis wrote:
>
> please_try_again;2217417 Wrote:
>> install the kernel sources and headers:
>>>
> Code:
> --------------------
> > > zypper in kernel-source kernel-devel kernel-desktop-devel kernel-default-devel
> --------------------
>>>
>> and try to recompile the vbox module:
>>>
> Code:
> --------------------
> > > service vboxdrv setup
> --------------------
>>>
>
> I have just faced the same problem with you but by just following your
> useful instruction i came up with the problem!!:wink:
>
> LET ME MAKE A NOTICE ABOUT THE COMMANDS (I USE OPENSUSE 11.4)
>
> The totally steps are :
>
>
> STEP 1 :
>
> -Install the kernerl sources and headers- :
>
>> zypper in kernel-source kernel-devel kernel-desktop-devel
>> kernel-default-devel
>
> STEP 2 :
>
> -Install the gcc compiler so as to compile the module!-
>
>> sudo zypper in gcc
>
> STEP 3 :
>
> -Install the appropiate service:-
>
>> sudo /sbin/service vboxdrv setup
>>
>
>
> My first post in openSUSE Forum. I hope that users who may face the
> same problem will be able to solve it!

/sbin/service is a redhat command IIRC. Maybe it’s in openSUSE too, but
normally when starting/stopping daemons in openSUSE you use rcCOMMAND,
i.e., ‘rcapache2 start’ or similar.

Further, to make virtualbox work, I’ve always used this:
/etc/init.d/vboxdrv setup

But even that isn’t necessarily required unless a kernel update comes
down the pike but no new virtualbox update at the same time. I intalled
via the virtualbox repository and ‘it just works’ as a rule.

HTH…

…Kevin

Kevin Miller
Juneau, Alaska
http://www.alaska.net/~atftb
“In the history of the world, no one has ever washed a rented car.”

  • Lawrence Summers
17

If you had a look at /sbin/service, you would have noticed that it does the same with some more checks.

18

/sbin/service is just a wrapper around /etc/init.d scripts for compatibility with people used to this Redhatism. rcfoobar is just a symlink for /etc/init.d/foobar and a SUSEism. If you ever sit for Linux exams you should use the /etc/init.d form as that’s the standard.

19

Hi everybody,

I have had this problem since March 2011 with Opensuse 11.4 amd64 / Gnome / Compiz…

found a way to get it work, just run

/etc/init.d/vboxdrv start

and Virtualbox will run fine.