Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this 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'm attempting to get VirtualBox OSE to run. I installed it with Synaptic, created a VM, and tried to start it. This came up:
Quote:
Virtual machine 'Win98box' has terminated unexpectedly during startup.
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
Machine
Interface:
IMachine {1e509de4-d96c-4f44-8b94-860194f710ac}
And then this:
Quote:
VERR_VM_DRIVER_NOT_INSTALLED (rc=-1908)
The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Re-setup the kernel module by executing
'/etc/init.d/vboxdrv setup'
as root. Users of Ubuntu or Fedora should install the DKMS package at first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.
I've searched for this extensively but nobody seems to have my problem. The solution I've found is to enter these commands into the terminal:
DKMS is installed, and I've reinstalled it several times. When reinstalling, this appears:
Quote:
user@computer ~ $ sudo aptitude reinstall dkms
[sudo] password for alkanetexe:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Writing extended state information... Done
The following packages will be REINSTALLED:
dkms
0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 19 not upgraded.
Need to get 0B/55.5kB of archives. After unpacking 0B will be used.
Writing extended state information... Done
(Reading database ... 105847 files and directories currently installed.)
Preparing to replace dkms 2.0.20.4-0ubuntu2.1 (using .../dkms_2.0.20.4-0ubuntu2.1_all.deb) ...
Unpacking replacement dkms ...
Processing triggers for man-db ...
Setting up dkms (2.0.20.4-0ubuntu2.1) ...
* Running DKMS auto installation service for kernel 2.6.27-11-generic * vboxdrv (2.0.4)... [fail]
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
user@computer ~ $
And as for the /etc/init.d/vboxdrv setup, this is the result:
I feel like an idiot. My genius friend explained everything to me and now I feel totally stupid for not seeing the problem myself. Thanks for your help, AlucardZero and Quakeboy02.
Last edited by alkanetexe; 04-11-2009 at 01:12 AM.
As root /etc/init.d/vboxdrv setup returns the usage phrase: {start|stop|restart|status} and as user sudo /etc/init.d/vboxdrv setup returns the same thing. I can't get this to work. what is wrong? Thanks.
OK, apparently we are running different VirtualBox from each other. In mine, there are more options. If you have installed from OSE source, then I think you need to RTFM again and go to where you compile and install the driver. If you have installed from a repository (you don't mention your distro) then you may have to download the driver module separately from your repo. In any case, the problem is that /dev/vboxdrv (i.e. the driver or kernel interface) is missing from your system, and it seems that your init.d script doesn't know how to make it.
I am using Mint. Mint provides a link to an installation program for VirtualBox. This is what I was using. Then when that didn't work, I went to the VirtualBox.org site and entered the command that they said would work:
Here everything seems to go fine untill linux-kernel-headers with this message:
Package linux-kernel-headers is a virtual package provided by:
linux-libc-dev 2.6.27-11.31
You should explicitly select one to install.
E: Package linux-kernel-headers has no installation candidate
I don't know if this is the problem or what to do about it if it is. Thanks.
Did you try installing linux-libc-dev? I don't know anything about Mint, but if you have synaptic, run that and install the linux-headers package for your kernel.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.