Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Installed VB on Fedora 14 ... all indications during installation normal. Tried to start VB and get this message:
Kernel driver not installed (rc=-1908)
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.
I then installed DKMS and executed the suggested file and got more errors about unloading DKMS and more problems. I need help or should I uninstall VB and try another Virtulization program?
I have played with that and after a while you can get it working. DKMS is a way to fix VB when your distro updates stuff so that VB also knows the change.
Personally I'd consider vmplayer but you can continue to try working this out. All the errors are well documented on other posts, I know because I had those too. Let us know if you want to continue or change.
Did you try running "/etc/init.d/vboxdrv setup"? That is the
command that compiles the kernel driver.
All dkms does is check at boot time if you have the driver
compiled for the current kernel. If it has not been compiled,
it will do that for you automatically. So let's start by
verifying that you have all the requirements to compile it
successfully.
OK here is what I got after installing dkms and then executing the /etc/init.d/vboxdrv setup
[ken@ken ~]$ su
Password:
[root@ken ken]# /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel modules [ OK ]
Uninstalling old VirtualBox DKMS kernel modules [ OK ]
Trying to register the VirtualBox kernel modules using DKMS
Error! Your kernel source for kernel 2.6.35.6-45.fc14.i686 cannot be found at
/lib/modules/2.6.35.6-45.fc14.i686/build or /lib/modules/2.6.35.6-45.fc14.i686/source.
[FAILED]
(Failed, trying without DKMS)
Recompiling VirtualBox kernel modules [FAILED]
(Look at /var/log/vbox-install.log to find out what went wrong)
[root@ken ken]#
I will now go to /var/log/vbox-install.log and return with whatever I find.
here is the install log from /var/log/vbox-install.log
Uninstalling modules from DKMS
removing old DKMS module vboxhost version 4.0.4
------------------------------
Deleting module version: 4.0.4
completely from the DKMS tree.
------------------------------
Done.
Attempting to install using DKMS
DKMS: add Completed.
You can use the --kernelsourcedir option to tell DKMS where it's located.
Failed to install using DKMS, attempting to install without
Makefile:167: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop.
To start a virtual machine in VirtualBox your system must be installed DKMS and GCC. You can do by using Terminal.
First of all, open your Terminal and type:su then enter your password to become root.
Second, type yum install dkms gcc into your Terminal to install DKMS and GCC.
Final, type /etc/init.d/vboxdrv setup. After that your VM should be started.
If you install Virtual Machine Additions in your VM you should install dkms.
Last edited by thuongquoc; 03-31-2011 at 01:10 PM.
Thank you for your response. I have done exactly as you have instructed. I still get the same results which I have posted above. I did open do to the "Build" script and "Source" scripts which point to the Kernal modules and they both state that they are broken and that the directory to which they point does not exist. I don't know how to install a kernal module in a certain directory to maybe fix this part. It is all a bit overwhelming to me. Thank you again and I do appreciate your help. From your name are you Vietnamese? We have a large Vietnamese population here in New Orleans and my wife is from South East Asia.
Did you do yum update? I have tried to install the newest VirtualBox in a fresh Fedora 14 in several time. It was successful.
I'm a first-year student in university in Vietnam.
I'm a fan of Fedora, too Why don't you try Fedora 15 GNOME 3 Alpha? I think it's very good. Beta Release will be publish on 2011-04-19.
Last edited by thuongquoc; 03-31-2011 at 09:58 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.