bassplayer Posted May 14, 2007 Report Share Posted May 14, 2007 I have Mandriva 2007 Spring (2007.1) with all updates and I configured a VirutalBox. When I try to start the VirtualBox I get an error stating that vboxdrv cannot be found. I try starting the VirualBox Daemon (e.g. /etc/init.d/virtualbox start) and I get the same error vboxdrv cannot be found. Shouldn't this work right out of the box? I have the powerpack edition and MCC states that virtualbox rpm was installed. What gives? Thanks! [moved from Software by spinynorman] Link to comment Share on other sites More sharing options...
jkerr82508 Posted May 14, 2007 Report Share Posted May 14, 2007 I believe that you need the dkms-virtualbox package and also the kernel-source-stripped package for your current running kernel. Do you have these installed? Jim Link to comment Share on other sites More sharing options...
bassplayer Posted May 15, 2007 Author Report Share Posted May 15, 2007 #rpm -q dkms-virtualbox returns: dkms-virtualbox-1.3.8-lmdv2007.1 How do I know if I have the kernel-source-stripped package? Also, I used MCC to remove the VirtualBox package that was installed during installation and downloaded the binary from www.virtualbox.org for Mandriva 2007.1 and installed it. These are the results I received: #rpm -i VirtualBox-1.3.8_mdv2007.1-1.i586.rpm Creating group 'vboxusers'. VM users must be member of that group! No precompiled module for this kernel found -- trying to build one. Messages emitted during module compilation will be logged to /var/log/vbox-install.log. Success! FATAL: Error inserting vboxdrv (/lib/modules/2.6.17-14mdv/misc/vboxdrv.ko) Invalid module format # The log file: /var/log/vbox-install.log looks good. No errors reported. I looked in the directory /lib/modules/2.6.17-14mdv/misc and the file is there: -rw-rw-r-- 1 root root 34478 May 14 21:03 vboxdrv.ko Any other suggestions? Thank you! Link to comment Share on other sites More sharing options...
bassplayer Posted May 15, 2007 Author Report Share Posted May 15, 2007 Also, I do see the vboxdrv file in /etc/init.d. Before this file was not there from the initial install from DVD. When I try to start the virtualbox daemon, I get the following message: # ./virtualbox start Starting virtualbox daemon: FATAL: Error inserting vboxdrv (/lib/modules/2.6.17-14mdv/misc/vboxdrv.ko): Invalid module format [FAILED] # I didn't reboot after the rpm installation. I'll reboot and see if that helped. Link to comment Share on other sites More sharing options...
bassplayer Posted May 15, 2007 Author Report Share Posted May 15, 2007 I rebooted the machine and selected the 2.6.17-14mdv kernel. Selected VirtualBox from the kde menu, configured my vm and selected start. I received the following message: Virtual Box kernel driver not installed. The vboxdrv kernel module was either not loaded or /dev/vboxdrv was not created for some reason. Re-setup the kernel module by executing '/etc/init.d/vboxdrv setup' as root. So as root: # ./vboxdrv setup Stopping VirtualBox kernel module [ OK ] Recompiling VirtualBox kernel module [ OK ] Starting VirtualBox kernel module FATAL: Error inserting vboxdrv (/lib/modules/2. 6.17-14mdv/misc/vboxdrv.ko): Invalid module format [FAILED] (modprobe vboxdrv failed) # Hopefully, all that is good information for you :) Link to comment Share on other sites More sharing options...
bassplayer Posted May 15, 2007 Author Report Share Posted May 15, 2007 Interesting enough after doing the above, I decided to reboot the machine. When loading up after the restart I received the following error in a dialog box that popped up: VirtualBox - Critical Error Failed to initialize COM or find the virtualbox COM server. Most likely, the virtualbox server is not running or failed to start. The application will now terminate Callee RC: 0x80004005 This is probably because the ./virtualbox start command fails... Link to comment Share on other sites More sharing options...
pmpatrick Posted May 15, 2007 Report Share Posted May 15, 2007 Those types of errors can occur if you compiled the vboxdrv module against a kernel source that is different from the kernel you are running. Check the output of: $ rpm -qa | grep kernel and: $ uname -a Make sure the kernel source you have installed corresponds to the kernel you are using. Link to comment Share on other sites More sharing options...
bassplayer Posted May 15, 2007 Author Report Share Posted May 15, 2007 Okay, I'll run both of those and see what the output is. I'm figuring it will be 2.6.17-14mdv kernel since that is the kernel I used when installing, when it compiled the kernel module (vboxdrv.ko) and the kernel that I selected at boot. Thanks! Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now