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.
i installed VirtualBox 4.2 on Linux (centos 6.2)
there isn't any problem, until as long as i want to start new os, an error is shown:
Code:
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. If it is available in your distribution, you should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary
the /etc/init.d/vboxdrv setup command results:
Code:
[root@ks28515 modules]# /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel modulesOpening /proc/modules: No such file or directory
Opening /proc/modules: No such file or directory
Opening /proc/modules: No such file or directory
[ OK ]
Uninstalling old VirtualBox DKMS kernel modules [ OK ]
Trying to register the VirtualBox kernel modules using DKMSError! echo
Your kernel headers for kernel 3.2.13-grsec-xxxx-grs-ipv6-64 cannot be found at
/lib/modules/3.2.13-grsec-xxxx-grs-ipv6-64/build or /lib/modules/3.2.13-grsec-xxxx-grs-ipv6-64/
source.
[FAILED]
(Failed, trying without DKMS)
Recompiling VirtualBox kernel modules [FAILED]
(Look at /var/log/vbox-install.log to find out what went wrong)
in /lib/modules folder just there is 2.6.32-220.13.1.el6.x86_64
all kernels already installed !! what should i do??!
I'm afraid I've shot my bolt. There's something going on here that's deeper than anything I've had to tackle.
Here's a thought: Not all distros install kernel headers and sources by default. I believe that CentOS is one that does not. See about installing the correct kernel headers and kernel-devel packages for the kernel you are using.
I'm afraid I've shot my bolt. There's something going on here that's deeper than anything I've had to tackle.
Here's a thought: Not all distros install kernel headers and sources by default. I believe that CentOS is one that does not. See about installing the correct kernel headers and kernel-devel packages for the kernel you are using.
You should be able to find the kernel-headers and the kernel-devel packages for your CentOS in the Add/Remove Software program, which is the GUI frontend for YUM. If you are not using a GUI, you can get them with YUM, but off the top of my head I don't know the exact syntax for installing them.
Distribution: Gentoo, Ubuntu, RHEL, CentOS, BSD, Solaris
Posts: 82
Rep:
Run (and post the result) to identify the kernel version you're using
Code:
uname -r
It seems like your vbox is looking for headers and modules for 3.2.13 but you only have them installed for 2.6.32. Maybe you've updated your kernel and not installed the updated headers? I'd start by checking that. Can you also supply the log /var/log/vbox-install.log ?
Distribution: Gentoo, Ubuntu, RHEL, CentOS, BSD, Solaris
Posts: 82
Rep:
Also, how did you install virtualbox? Did you configure and compile from source? and I forgot to ask if you have netboot disable in bios as this can create issues as well.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.