[SOLVED] modprobe vboxdrv error.. I'm stuck for 3days
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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 using Slackware and quite new in Slackware and Linux
I just want to use Virtual Box..
I went to SlackBuild.org and downloaded virtualbox and requirements
(virtualbox-kernel and acpid)
Then I ran virtualbox but I can't add new VM because of vboxdrv
I googled and googled.. and find out that this is because of kernel module ..maybe?
When I did
Code:
modprobe vboxdrv
And result is
Code:
modprobe: ERROR: could not insert 'vboxdrv': Exec format error
and I did dmesg to find out why
Code:
dmesg
result is
Code:
[ 4694.215588] vboxdrv: version magic '3.10.17-smp SMP mod_unload PENTIUMIII ' should be '3.10.17 mod_unload 486 '
What it means.. and what is version magic and What should I do?
You don't need to use the slackbuild. download virtualbox directly from virtualbox.org and make sure you get the bundel installer. This installed will setup everything for you.
You don't need to use the slackbuild. download virtualbox directly from virtualbox.org and make sure you get the bundel installer. This installed will setup everything for you.
What was the error you got from the bundle installer? Are you using Slackware 32bit or 64 bit? (or multi-lib)?
I'm using 32bit
and bundle installer is..
did you mean this?
Code:
bash-4.2# /root/Downloads/VirtualBox-4.3.6-91406-Linux_x86.run
Verifying archive integrity... All good.
Uncompressing VirtualBox for Linux installation............
VirtualBox Version 4.3.6 r91406 (2013-12-18T16:23:31Z) installer
Installing VirtualBox to /opt/VirtualBox
Python found: python, installing bindings...
Building the VirtualBox kernel modules
VirtualBox has been installed successfully.
You will find useful information about using VirtualBox in the user manual
/opt/VirtualBox/UserManual.pdf
and in the user FAQ
http://www.virtualbox.org/wiki/User_FAQ
We hope that you enjoy using VirtualBox.
bash-4.2# virtualbox
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
available for the current kernel (3.10.17) 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.
bash-4.2# /etc/rc.d/rc.vboxdrv setup
Stopping VirtualBox kernel modules ...done.
Removing old VirtualBox pci kernel module ...done.
Removing old VirtualBox netadp kernel module ...done.
Removing old VirtualBox netflt kernel module ...done.
Removing old VirtualBox kernel module ...done.
Recompiling VirtualBox kernel modules ...done.
Starting VirtualBox kernel modules ...failed!
(modprobe vboxdrv failed. Please use 'dmesg' to find out why)
bash-4.2#
(modprobe vboxdrv failed. Please use 'dmesg' to find out why)
Did you try that? Have you done a full install of Slackware? Another possibility: depending on your processor, you might be getting the kvm (either amd or intel) module loaded automatically, this can interfere sometimes with VirtualBox. Try running:
That could be causing the problem, but I'm only guessing. Try, as root:
Code:
modprobe -r kvm_intel
Then installing and running VirtualBox.
Thanks! it worked
But I still got problems
When I reboot computer and in lsmod kvm_intel appears again
Is there a way to remove kvm_intel?
And what was kvm_intel anyway?
It works with qemu to run virtual machines. I have kvm_amd loaded automatically, so when I get round to using VBox on 14.1, I'm going to be facing the same problem. I think you can blacklist it with a file in either /etc/modprobe.d or /lib/modprobe.d (there's some files in there could be used as a sample).
I am using Porteus 3.0 64 bits as guest on a Linux Mint 17 Quina -64 bits
When I try to build vbox addons, I get the error picture I attached . I tried to replace the kernel.xzm in /mnt/sda1/porteus/base/
but i'm still turning arons again and again !
Commands like apt-get update , yum do not work !
What must I do ??!I'm also stuck still a week !
Thank you so much in advance and for the guidance you provide to dummies like me !LOL!
Caron
Rodrigues Island
Republic of Mauritius
Indian Ocean
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.