Virtual box problem

Nobody999 · #1 26th June 2012, 01:52 AM

Hello, I am running F17 and after install updates yesterday one of which was a kernal update i get the following error when trying to start a virtual machine OS:

Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver (vboxdrv) is probably not loaded.

If you installed or VirtualBox OSE package recently you need to restart the computer for the driver to load.

Alternatively, you may attempt to load the driver by issuing the following command with system administrator (root) privileges:

'/etc/sysconfig/modules/VirtualBox-OSE.modules'

After running the cammand the error log told me to run i get the following from the terminal

[Kevins@Wardriver999 Kevins]$ /etc/sysconfig/modules/VirtualBox-OSE.modules
bash: /etc/sysconfig/modules/VirtualBox-OSE.modules: No such file or directory
[Kevins@Wardriver999 Kevins]$

I have looked online for a fix but i cannot seem to find any that work. Does anyone here have a fix for this problem? Thank you in advance.:confused

mikee · #2 26th June 2012, 03:56 AM

Do this to see if the modules are loaded:

]# /etc/init.d/vboxdrv status
VirtualBox kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) are loaded.

You can rebuild them for a newer kernel like this:

# /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel modules [ OK ]
Uninstalling old VirtualBox DKMS kernel modulesError! There are no instances of module: vboxhost
4.1.18 located in the DKMS tree.
[ OK ]
Trying to register the VirtualBox kernel modules using DKMS[ OK ]
Starting VirtualBox kernel modules [ OK ]

Nobody999 · #3 26th June 2012, 09:02 PM

Quote:

Originally Posted by mikee

Do this to see if the modules are loaded:

]# /etc/init.d/vboxdrv status
VirtualBox kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) are loaded.

You can rebuild them for a newer kernel like this:

# /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel modules [ OK ]
Uninstalling old VirtualBox DKMS kernel modulesError! There are no instances of module: vboxhost
4.1.18 located in the DKMS tree.
[ OK ]
Trying to register the VirtualBox kernel modules using DKMS[ OK ]
Starting VirtualBox kernel modules [ OK ]

O k I ran the first command and this is what I got:

[Kevins@Wardriver999 /]$ /etc/init.d/vboxdrv status
bash: /etc/init.d/vboxdrv: No such file or directory

The last time I installed updates I had the same problem with vbox so I uninstalled it and reinstalled it and it worked fine after that but I was trying to avoid doing that again.

I also ran the rebuild command and I get the following:

bash: /etc/init.d/vboxdrv: No such file or directory
[Kevins@Wardriver999 /]$

I don't know maybe I am in the wrong direstory. I ran theses command in root.

nonamedotc · #4 26th June 2012, 09:49 PM

Do you have kernel-devel installed? Try

Code:

yum install kernel-devel

Or update kernel-devel if installed already and not updated.

Nobody999 · #5 26th June 2012, 10:36 PM

Quote:

Originally Posted by nonamedotc

Do you have kernel-devel installed? Try

Code:

yum install kernel-devel

Or update kernel-devel if installed already and not updated.

I ran the yum install command for kernel-devel and it appears that i have the latest version.

Package kernel-devel-3.4.3-1.fc17.x86_64 already installed and latest version
Nothing

This is used to compile kernel modules as you know but i am not sure how to use this in this situation. I fyou can show me what to do since i have this installed already? Thank you.

geeeHUn · #6 30th June 2012, 02:34 PM

gcc installed? if i remember right, that will need to compile it, also dkms and you need to add your username to the "vboxusers" group.

KenJackson · #7 1st July 2012, 02:42 AM

Quote:

Originally Posted by Nobody999

O k I ran the first command and this is what I got:

[Kevins@Wardriver999 /]$ /etc/init.d/vboxdrv status
bash: /etc/init.d/vboxdrv: No such file or directory

That looks like the file /etc/init.d/vboxdrv is missing altogether.
That file is part of the VirtualBox package.
Try:
rpm -q "VirtualBox*"

If it's not installed, try:
sudo yum install VirtualBox

As a side note, I just noticed I still have VirtualBox-4.0-4.0.14 installed and it wasn't upgraded to Oracle's VirtualBox-4.1 when I did yum update. I wonder what's up with that.

cheerio158 · #8 8th July 2012, 03:41 PM

Quote:

Originally Posted by KenJackson

That looks like the file /etc/init.d/vboxdrv is missing altogether.
That file is part of the VirtualBox package.
Try:
rpm -q "VirtualBox*"

If it's not installed, try:
sudo yum install VirtualBox

As a side note, I just noticed I still have VirtualBox-4.0-4.0.14 installed and it wasn't upgraded to Oracle's VirtualBox-4.1 when I did yum update. I wonder what's up with that.

I had the same problem after updating to kernel-3.4.4-5.fc17.x86_64. Virtualbox was working fine before that.

To resolve, I performed:

# yum erase VirtualBox
# yum install VirtualBox
# /etc/sysconfig/modules/VirtualBox.modules

This time, the modules existed and were inserted. Some hiccup happened somewhere.

My version of Virtualbox:

$ rpm -qa|grep -i virtualbox
VirtualBox-4.1.16-6.fc17.x86_64
kmod-VirtualBox-3.4.4-5.fc17.x86_64-4.1.16-1.fc17.5.x86_64

subxel · #9 10th July 2012, 09:40 AM

I had the same problem:

did the following:
# yum erase VirtualBox
# yum install VirtualBox
# yum update

and then it worked.

davak · #10 12th July 2012, 10:43 AM

Yea, it's pain it the ass, it actually happens anytime kernel is updated. Well, my temporary "dirty" solution is adding following alias to /root/.bashrc (and then using that alias instead of standard upgrade cmd)

Code:

alias upgrade='yum upgrade && yum erase VirtualBox && yum install VirtualBox && /etc/sysconfig/modules/VirtualBox.modules'

I don't consider this a good solution though. Does anyone have any better ideas?

D.

#11 12th July 2012, 10:56 AM

Quote:

Originally Posted by davak

Yea, it's pain it the ass, it actually happens anytime kernel is updated. Well, my temporary "dirty" solution is adding following alias to /root/.bashrc (and then using that alias instead of standard upgrade cmd)

Code:

alias upgrade='yum upgrade && yum erase VirtualBox && yum install VirtualBox && /etc/sysconfig/modules/VirtualBox.modules'

I don't consider this a good solution though. Does anyone have any better ideas?

D.

Code:

su
yum install akmod-VirtualBox

davak · #12 19th July 2012, 03:00 PM

Works great! I consider this solved.

VN1980 · #13 26th July 2012, 01:21 PM

Hi
As an end user I found that Virtual Box works well immediately on installation of Fedora and some 3 or 4 Kernel Upgrades. After that, it does not work. What ever the solutions are given by Forum People or other internet pages, it does not work. By the time we get frustrated and feel totally gone, a new release of Fedora Comes and the issue is postponed for another 6 months. This is my experience since I started using Fedora 15 to till date.

Now I simply at boot menu select the lowest kernel in which Virtual Box Worked and works on it in case of need.

Yours
VN