I can see this error occurring in multiple past versions of suse. The answer seems to involve recompiling the open source version of VBox, but this is surely overkill. Isn't there a way to either a)get the right kernel version of VBox for 11.3 or b)set whatever permissions are required.
In all the answer so far I can't see a solution I can understand for these combinations, sues 11.3 and VBox 3.2.8. The error is consistent, and if the install doesn't work properly (it took my a few attempts even to install it without error messages) then surely its an issue either for Oracle or Suse? It runs ok but hwen trying to fire up a newly created XP VM this error message occurs trying to switch from W764bit to suse11.3 64bit
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've dkms installed and did a reboot as well.
when I open virtualbox OSE and tried to run a vm i get this error
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. Re-setup 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. So i tried doing what it said and I got this error when i tried to run /etc/init.d/vboxdrv setup (as root)
Code:
Stopping VirtualBox kernel module done Recompiling VirtualBox kernel module, NOT. It has been packaged.Recompiling VirtualBox
[code]....
Then i ran dmesg and there was a ton of stuff that seemed to be unreleated so i ran dmesg -c to clear it. then i ran the vboxdrv this again then checked dmesg again expecting there to be nothing but the vboxdrv stuff but it was still blank.I really dont know what to do at this point I tried uninstalling and reinstalling but that makes no difference
I tried to install the new Vbox 3.2.6 through rpm as a guide told me but I first had errors with the older vbox dependencies, so I uninstalled vbox 3.1.8.2 and now I am with a vbox period. Is there something I can do to fix this I tried this tutorial didn't work for me [URL] and another on the fedora forum (lost the history). error I get is Recompiling VirtualBox kernel module [FAILED] and 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.
I upgraded to Lucid last night, and I'm getting this error when I try to run virtualbox-ose:
Quote: Kernel driver not installed (rc=-190 Please install the virtualbox-ose-dkms package and execute 'modprobe vboxdrv' as root. I try it, then I get: Quote: modprobe vboxdrv FATAL: Module vboxdrv not found.
I have no idea what's going on. Can anyone help? The version of virtualbox is 3.1.6-dfsg-2ubuntu2
I was trying to install VirtualBox through the YaST > Software Management but it is not working, someone in the forum told me that I have to download the OSE version and do it manual way. Finally I am able to start up VB but not able to use the network connection. Thus I am trying to do this:
/etc/init.d/vboxdrv setup. I get this error:
[code]...
When I type dmesg, it shows me a bunch of info which I don't know what should look for. When I type modprobe vboxnetflt, I get the error: FATAL: Error inserting vboxnetflt (/lib/modules/2.6.37.1-1.2-default/updates/vboxnetflt.ko): Invalid module format. what should I do in order to get my VB to be able to connect to the internet?
I'm just installed OpenSuse 11.3 (64) on a 30gb SSD, hoping to get virtualbox 4.0 running to virtualize an instance of Windows 7.I went through some pain with my Nvidia video card and actually getting vb to install, but through lots of searching and tinkering got here.I created a vm in the vb control panel, but when I go to start it I get:
Code: Failed to open a session for the virtual machine Win7Main. The virtual machine 'Win7Main' has terminated unexpectedly during startup with exit code 1.
I have checked the known issues and the sticky post, it does not seem to be related. I have Ubuntu as my host OS and I want to run Windows as a guest.
Now, Here is the error:
Quote:
Kernel driver not installed (rc=-190
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 have done the obvious:
I still have the same error. I just updated from Ubuntu 10.04 to 10.10, then I was prompted by virtual box to update to the newest version, then this happened.
When I start up a virtual machine in Virtualbox on Suse 13.1 I see 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 have downloaded vbox from its site and installed it. I created a vm but when I try to start it, I get error: 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.
And when I try 'sudo /etc/init.d/vboxdrv setup', I get: Stopping VirtualBox kernel modules done Uninstalling old VirtualBox DKMS kernel modules done Trying to register the VirtualBox kernel modules using DKMS failed (Failed, trying without DKMS) Recompiling VirtualBox kernel modules failed (Look at /var/log/vbox-install.log to find out what went wrong)
And this is /var/log/vbox-install.log: Makefile:159: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop.
my error when trying to run a VB (Virtualbox). Error as copied from error box. install the virtualbox-ose-modules package for your kernel and execute 'modprobe vboxdrv' as root. VBox status code: -1908 (VERR_VM_DRIVER_NOT_INSTALLED).
[code]...
I get this when trying to launch a VB after making one with wizzard.
Each time I try to run my Windows virtual box, I got this error: Quote: Kernel driver not installed (rc=-190
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. Which is fine, so I run sudo /etc/init.d/vboxdrv setup as requested and then it works. But I have to do this EVERY TIME I use Virtual box. This step takes a minute or two to do its thing, so it's quite time consuming.
I had no problems up to the newest kernel version. But for 2.6.40-4 akmods fails to build the kmod with the following error:
Code: Building RPM using the command '/usr/bin/akmodsbuild --target x86_64 --kernels 2.6.40-4.fc15.x86_64 /usr/src/akmods/VirtualBox-OSE-kmod.latest' Building modules, stage 2. MODPOST 1 modules CC /tmp/akmodsbuild.yob64XwN/BUILD/VirtualBox-OSE-kmod-4.0.4/_kmod_build_2.6.40-4.fc15.x86_64/vboxnetflt/vboxnetflt.mod.o LD [M] /tmp/akmodsbuild.yob64XwN/BUILD/VirtualBox-OSE-kmod-4.0.4/_kmod_build_2.6.40- [Code]...
There was a kernel update included in my last three attempts of online updating SuSE 11.2 -- all of which which ended with an error, something like kernel rpm could not be installed (one can't copy that out of the YAST-window ).
The new kernel-relevant directories are there under /boot, the original 2.6.31.5 is gone. This produced lots of errors during the next boot until I manually re-assigned links in /lib/modules pointing to the new kernels. "uname -a" shows my old kernel (see also this thread: [url].
I ran "rpm --rebuilddb" and re-tried the installation, all to no avail.
In the message box during install came about 1,5 MB of errors, a brief extract is shown below:
Code:
Any ideas how to proceed? Can one delete the rpm database and rebuild it from the online repositories?
I have downloaded latest version of sun vm virtual box foe Fedora 13 x64. After installing and creating a VM when I want to start vm I got this error. And when I enter this command on terminal : /etc/init.d/vboxdrv setup
I get this error: Code: [root@localhost arash]# /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) Log file:
Code: [root@localhost arash]# cat /var/log/vbox-install.log Makefile:159: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop. [root@localhost arash]#
uname -r prints 2.6.18-164.el5 Yum install kernel-headers/kernel-devel gives me 2.6.18-194 When trying to run virtualbox I get an error: Kernel Driver not installed: (rc=-1908) Please reinstall the kernel module by running "/etc/init.d/vboxdrv setup" as root...
/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 headers for kernel 2.6.18-164.el5 cannot be found at /lib/modules/2.6.18-164.el5/build or /lib/modules/2.6.18-164.el5/source. [FAILED] (Failed, trying without DKMS) Recompiling VirtualBox kernel modules [FAILED] (Look at /var/log/vbox-install.log to find out what went wrong)
I'm assuming the setup program is using the output from uname -r to determine the kernel, the problem is the kernel sources I've got from yum do not jibe with the uname value.
I installed the latest kernel liquorix (2.6.35) but when i want to install the Nvidia driver downloaded on the Nvidia website (256.53), i have an error message because Nvidia doesn't found the kernel source tree.
I install linux-image-2.6.35-6.dmz.2-liquorix-686_2.6.35-16_i386.deb, linux-headers-2.6.35-6.dmz.2-liquorix-686_2.6.35-16_i386.deb and build-essential. I don't understand why the installation doesn't works.
I have tried using cairo-dock but not much impressed as its more flashy(installation was very easy ), Today i tried installing simdock which is showing me some error like. checking for wx-config... no configure: error:wxWidgets must be installed on your system. check that wx-config is in path, the directory where wxWidgets libraries are installed (returned by 'wx-config --libs' or 'wx-config --static --libs' command) is in LD_LIBRARY_PATH or equivalent variable and wxWidgets version is 2.8.0 or above "How to get thru this problem.
I'm using Slackware 13.1 32bit and can't run virtualbox when I try to boot the virtual machine it shows me a window with the following message:
Quote:
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' run - /etc/rc.d/rc.vboxdrv setup
Quote:
Stopping VirtualBox kernel module ...done. Recompiling VirtualBox kernel module ...failed! (Look at /var/log/vbox-install.log to find out what went wrong) Check /var/log/vbox-install.log
Quote:
make KBUILD_VERBOSE=1 -C /lib/modules/2.6.33.4-smp/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 modules test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( echo;
I am running Lenny and using VirtualBox OSE 1.6.6. In order to try squeeze I installed it in a VM. I tried to install Guest Additions also, but i get this error:
VirtualBox 1.6.6 Guest Additions installation Building the VirtualBox Guest Additions kernel module... Building the shared folder support kernel module... Unable to build the kernel module.
I checked what /var/log/vboxadd-install.log had to say:
/usr/src/linux-headers-2.6.32-5-common/include/net/neighbour.h:115: error: variably modified a at file scope /tmp/vbox.0/utils.c: In function 'sf_path_from_dentry:
[code].....
I tried with 3 versions of the kernel 2.6.32-5-686,2.6.32-5-484,2.6.32-3-686 but I cannot get it to work using any of them. Also I tried to install version 2.6.30-2-686 but I couldn't since synaptic said that it Depends: linux-kbuild-2.6.30 but it is not installable.
I was tryin to install virtualbox on Suse Linux Enterprise Desktop 11 and it said it needs pad-devil. I looked in the software archive that came with sled 11 but it wasnt there. I tried downloading the VirtualBox install for Suse Linux Enterprise Server but got the same error as when i tried install VirtualBox with the opensuse 11.1 rpm file. can virtualbox even be install on sled? (has anyone done it?) and if so where can i find pam-devil?
I have a box already has openSuse 11 32bits installed. I want to replace it with openSuse 11 64 bits. When I insert the openSuse 11 64 bits CD, I got error message "this is a 32 bit computer. Can not use 64 bit software". so How do I wipe out the old OS (32 bits), and install new OS (64 bits)?
I am trying to perform a patch on the current kernel version that was included in SLES SP1 and do a compile of the kernel. However, after installing the new kernel and rebooting, I got a "Waiting for device" error. I tried just compiling the kernel after a fresh installation of SLES SP1 on a physical and virtual machine and got the same problem. When I was doing make rpm, I got errors something like (can't remember but it was something like not in gzip format, file format not recognized and exec format error). Also, what I noticed when performing mkinitrd was that there were errors like the following:
ERROR: modinfo :could not open /var/tmp/kernel-2.6.32.120.7paemod-root/lib/modules/2.6.32.12-0.7-pae-mod/kernel/drivers/char/agp/ali-agp.ko: No such file or directory
The files include others such as amd-k7-agp.ko, ati-agp.ko, efficeon-agp.ko and others. There are also 2 files in the usb direcotry that has this problem. This happened even after a fresh installation. What I did was the following:
cd /usr/src/linux make cloneconfig make menuconfig make rpm mkinitrd vim /boot/grub/menu.lst
I opted to install my Linux Fedora distribution, in a SUN VM (Virtualbox). [URL] I have 2 questions:
My current max res available to select is 1024x768. Can I run at 1920x1200? My display indicated that it is 'Unknown'. I don't know if that is in on the deal, or not...
Second question: When installing VBOXADDITIONS_3.1.2_56127, I am getting the error: Building the VirtualBox Guest Additions kernel modules [FAILED]
If I am displaying the log correctly, it indicates: Makefile:23: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again.. Stop Pictures are located here, in the EVGA Linux forum: [URL] I am new to both Linux, and Fedora.
My mission statement: To run Linux using the Fedora distribution, in a VM window under Windows 7 64bit Ultimate, with the ability for scripting using Bash, with the Perl programming language installed, and use Apache Tomcat to monitor both apps, and various VM installs, on numerous Servers via the internet.
This has got me stumped. I expected to do /etc/init.d/vboxdrv setup after the upgrade from 11.3 to 11.4 but the command fails. The log is (it seems to repeat so I only quote the final bits to make it fit into the wordcount limit):
Code: make KBUILD_VERBOSE=1 -C /lib/modules/2.6.37.1-1.2-desktop/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 modules
I have been having some problems with virtualbox starting. So here is the issue: When I start a VM I get the following: 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. reinstall the kernel module by executing
[code]...
I am seeing quite a few entries about the usb. I am not sure if that is common or if its unrelated. I am running x86 11.3, and virtualbox 4.0.4 I have tried to uninstall, and even go back to 3.2
I just up-graded to the latest version of the stable 11.4 64bit kernel on my laptop and it appears that the repositories have not compiled the VirtualBox driver module for the current kernel ... When I make /vboxdrv setup the message is:
Recompiling VirtualBox vboxadd kernel module, NOT. It has been packaged
I think this means that the installed module will not recompile has it was packaged. My kernel version is the lattest :
2.6.37.6-0.5-1
And my VirtualBox was installed from the Virtualization repos (4.0.8.11-1) even made the Vendor change and all. The version Before the lattest (4.0.4-1.6) did not work either. With the same problem. It is very easy to install VirtualBox from the Sun site and every time there is a Kernel up-date one can always make /etc/vboxdrv setup.
I'm currently trying to add OpenSUSE to my Laptop which already has Vista Ultimate installed, hoping I will end up with a dual boot system. Currently, my HD is divided into four partition: Vista Ultimate with Bitlocker enabled needs two partitions - one for the unencrypted boot files, and one for the rest of the system. Then I have an unencrypted partition for data that I don't want encrypted, and finally the partition in which I plan to install Linux.
I have already installed OpenSUSE to that fourth partition, and it worked just fine. But now, I'd like to reinstall with LVM, so that I can use encryption as well. Upon installation, however, I get the following error: Code: Error Failure occurred during following action: Creating volume group system fromv System error code was: -4004 I'm wondering if this is because I'm running out of (primary?) partitions? Seems like LVM, just like Vista Ultimate, needs two partitions, one for the boot files and one for the rest of the system. I've read something about a PC drive only being able to hold four partitions, so I'm wondering if I need to get rid of that extra unencrypted partition I have in order to get OpenSUSE with LVM installed. Or am I barking up the wrong tree?