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.
It may just be that the vboxdrv module has not been started.
Have a look at /etc/default/virtualbox-ose and see if the driver has been set to load automatically:
Code:
LOAD_VBOXDRV_MODULE=1
Then see if the module starts:
Code:
sudo /etc/init.d/virtualbox-ose start
If your installation is different and doesn't have these files, just try inserting the module directly:
Code:
sudo modprobe vboxdrv
sudo modprobe vboxnetflt
If modprobe cannot find the kernel modules, they need to be installed or built. They will have a package name something like virtualbox-ose-modules-2.6.686. They can also be built from source (there will be details in other posts).
Last edited by neonsignal; 11-09-2009 at 02:40 AM.
I installed virtual box and was able to set up the vm, but when I try to run it I get this message:
WARNING: The vboxdrv kernel module is not loaded. Either there is no module available for the current kernel (2.6.30.10-105.fc11.i686.PAE) or it failed to load. Please recompile the kernel module and install it by
sudo /etc/init.d/vboxdrv setup
You will not be able to start VMs until this problem is fixed.
I do the command and I get this:
[root@FrankLaptop Frank]# sudo /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel module [ OK ]
Recompiling VirtualBox kernel module [FAILED]
(Look at /var/log/vbox-install.log to find out what went wrong)
[root@FrankLaptop Frank]# /var/log/vbox-install.log
bash: /var/log/vbox-install.log: Permission denied
I don't know what to do from this point can you please help?
Last edited by FrankRhoades; 01-22-2010 at 04:27 PM.
Chances are that you can't compile it because you don't have the headers for your kernel installed (linux-headers-2.6-686).
However, instead of compiling your own vboxdrv, some distros already have precompiled versions. Have a look for a package called something like virtualbox-ose-modules-2.6-686 (it might not be exactly that, but it will start with 'virtualbox-ose-modules').
If you still have problems, I would suggest starting a new forum thread, so it doesn't get confused with the original post.
Last edited by neonsignal; 01-22-2010 at 08:13 PM.
Thanks for the help. I posted a new thread for this problem; Getting Virtual Box to run XP problem with the /etc/init.d/vboxdrv setup. I am still having problems, but I know what the initial issue was. I posted it under the new thread. Thanks again.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.