Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

I want to run VirtualBox on Ubuntu, it used to work a while ago but I can't remember when or why. However when I double-click on an OS to run, it tries to start - opens a window for the virtual OS, gives the "host key" message, but then 5 seconds later closes the OS window and gives this error:

Failed to load VMMR0.ro (VERR_SUPLIB_OWNER_NOT_ROOT)


Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: 
Console
Interface: 
IConsole {1968b7d3-e3bf-4ceb-99e0-cb7c913317bb}

If I run it with sudo virtualbox I still get the same problem. I've tried sudo apt-get purge virtualbox then sudo apt-get install virtualbox. I notice during the re-installation I get this amongst all the other output on the console:

Setting up virtualbox (4.1.12-dfsg-2ubuntu0.1) ...
 * Stopping VirtualBox kernel modules                                    [ OK ] 
 * Starting VirtualBox kernel modules
 * No suitable module for running kernel found                           [fail]

Any ideas?

share|improve this question
    
If I delete /home/duncan/.virtualbox and /home/duncan/VirtualBox VMs and start from scratch the error still occurs. However I remember VirtualBox working at one point so any other ways to reset settings may help. –  duncan Aug 3 '12 at 20:52
    
just type this in terminal, sudo apt-get install virtualbox-dkms , if already exist reinstall and you ready to go. –  Shaharil Ahmad Sep 5 '13 at 13:53
add comment

10 Answers 10

Solved the problem on my Ubuntu 12.04 install

sudo apt-get purge virtualbox
sudo apt-get install build-essential linux-headers-`uname -r`
sudo dpkg -i ~/download_folder/virtualbox-4.2_4.2.12-84980~Ubuntu~precise_i386.deb

You can get the .deb files here

This pretty much did it for me!

share|improve this answer
add comment

I had the very same problem and it helped to install linux-headers for current kernel and reinstalled virtualbox-dkms and dkms.

share|improve this answer
add comment
up vote 0 down vote accepted

Resolved here. Have some serious permission problems and need to do a clean install.

share|improve this answer
5  
Please provide the content in your link for others to see easily and so the information is preserved should the linked content be moved/deleted. –  weberc2 Feb 2 '13 at 21:20
add comment

In my case I use

sudo apt-get purge virtualbox

before reinstalling it.

share|improve this answer
add comment

Installed VirtualBox packages from Ubuntu 12.10 repositories. Did NOT purge Virtualbox packages nor downloaded or installed foreign debs.

Installed dkms, linux-source and linux-headers-3.5.0-23

(uname -r output was 3.5.0-23-generic)

Restarted VirtualBox.

Everything worked fine

share|improve this answer
add comment

It seems to be a problem of permission. Try:

sudo chown root:root /usr
sudo chown root:root /usr/lib
sudo chown root:root /usr/lib/virtualbox

You can have a look at this ticket for more information.

share|improve this answer
add comment

For me just using apt-get was enough:

sudo apt-get install virtualbox
share|improve this answer
add comment

Sounds like your vboxnetflt module is not loaded. Run this:

sudo modprobe vboxnetflt
share|improve this answer
add comment

/etc/init.d/virtualbox start is trying to find a module vboxdrv for your current kernel... (/lib/modules/`uname -r` -name "vboxdrv.*). Please install linux-headers and try start again...

share|improve this answer
    
Does it help to refer to askubuntu.com/questions/138079/… ? –  John S Gruber Aug 4 '12 at 3:41
    
That command is incorrect, and installing linux-headers doesn't have any impact on the issue. –  weberc2 Feb 2 '13 at 21:29
add comment

In my case ubuntu 12.10 64! I downloaded virtualbox-4.2_4.2.6-82870~Ubuntu~quantal_amd64

sudo apt-get purge virtualbox-4.2  
sudo apt-get purge virtualbox-guest-additions-iso  

sudo apt-get install linux-headers-3.5.0-21-generic  
sudo dpkg -i virtualbox-4.2_4.2.6-82870~Ubuntu~quantal_amd64.deb  
share|improve this answer
    
This doesn't fix the issue at all... It's just another way of getting the same error messages. –  weberc2 Feb 2 '13 at 21:27
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.