LinuxQuestions.org - [SOLVED] modprobe vboxdrv error.. I'm stuck for 3days

- Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)

- - modprobe vboxdrv error.. I'm stuck for 3days (https://www.linuxquestions.org/questions/linux-newbie-8/modprobe-vboxdrv-error-im-stuck-for-3days-4175493638/)

modprobe vboxdrv error.. I'm stuck for 3days

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?

Quote:

Originally Posted by gonny95 (Post 5110976)

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.

Quote:

Originally Posted by /dev/random (Post 5110998)

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.

I also tried but didn't work either.

Quote:

Originally Posted by gonny95 (Post 5111000)

I also tried but didn't work either.

What was the error you got from the bundle installer? Are you using Slackware 32bit or 64 bit? (or multi-lib)?

Quote:

Originally Posted by /dev/random (Post 5111003)

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#

http://i62.tinypic.com/4kgnr5.png
these are my kernel-headers

and when I type uname -r

Code:

bash-4.2# uname -r

3.10.17

In the directory /lib/modules/

Code:

bash-4.2# ls /lib/modules/

3.10.17  3.10.17-smp

what's wrong with my linux:cry:

(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:

Code:

lsmod

and

Code:

cat /proc/cpuinfo

And post the results.

Results are:

Code:

bash-4.2# lsmod

Module                  Size  Used by

parport_pc            16472  0 

cdc_acm                13933  0 

ipv6                  234918  14 

lp                      7474  0 

ppdev                  4702  0 

parport                24879  3 lp,ppdev,parport_pc

fuse                  64207  3 

hid_generic              733  0 

usbhid                31706  0 

hid                    70115  2 hid_generic,usbhid

usb_storage            35805  0 

nouveau              870054  3 

coretemp                3855  0 

acpi_cpufreq            4479  1 

mperf                    911  1 acpi_cpufreq

snd_hda_codec_hdmi    26486  4 

mxm_wmi                1119  1 nouveau

gpio_ich                3424  0 

wmi                    7051  2 mxm_wmi,nouveau

ttm                    44502  1 nouveau

drm_kms_helper        31326  1 nouveau

drm                  184126  5 ttm,drm_kms_helper,nouveau

i2c_dev                4471  0 

r8169                  50804  0 

snd_hda_codec_realtek    30108  1 

kvm_intel            119260  0 

kvm                  306633  1 kvm_intel

i2c_i801              12385  0 

i2c_algo_bit            4567  1 nouveau

i2c_core              17440  6 drm,i2c_i801,i2c_dev,drm_kms_helper,i2c_algo_bit,nouveau

uhci_hcd              19323  0 

ehci_pci                2972  0 

video                  10162  1 nouveau

processor              20557  1 acpi_cpufreq

snd_hda_intel          29246  2 

snd_hda_codec        123857  3 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_intel

snd_hwdep              4730  1 snd_hda_codec

snd_pcm                60504  3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel

snd_page_alloc          5894  2 snd_pcm,snd_hda_intel

snd_timer              14195  1 snd_pcm

snd                    43944  11 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec,snd_hda_intel

soundcore              4218  1 snd

ehci_hcd              33259  1 ehci_pci

thermal_sys            18829  2 video,processor

intel_agp              8672  0 

button                  3664  1 nouveau

evdev                  7448  5 

intel_gtt              10108  1 intel_agp

lpc_ich                11181  0 

freq_table              2104  2 acpi_cpufreq,thermal_sys

agpgart                21576  4 drm,ttm,intel_agp,intel_gtt

hwmon                    997  3 coretemp,nouveau,thermal_sys

mii                    3263  1 r8169

microcode              7469  0 

loop                  14679  0

Code:

bash-4.2# cat /proc/cpuinfo

processor        : 0

vendor_id        : GenuineIntel

cpu family        : 6

model                : 23

model name        : Pentium(R) Dual-Core  CPU      E5800  @ 3.20GHz

stepping        : 10

microcode        : 0xa0b

cpu MHz                : 3200.000

cache size        : 2048 KB

fdiv_bug        : no

f00f_bug        : no

coma_bug        : no

fpu                : yes

fpu_exception        : yes

cpuid level        : 13

wp                : yes

flags                : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm xsave lahf_lm dtherm tpr_shadow vnmi flexpriority

bogomips        : 6384.79

clflush size        : 64

cache_alignment        : 64

address sizes        : 36 bits physical, 48 bits virtual

power management:

From lsmod:

Code:

kvm_intel            119260  0 

kvm                  306633  1 kvm_intel

That could be causing the problem, but I'm only guessing. Try, as root:

Code:

modprobe -r kvm_intel

Then installing and running VirtualBox.

Quote:

Originally Posted by brianL (Post 5111120)

From lsmod:

Code:

kvm_intel            119260  0 

kvm                  306633  1 kvm_intel

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).

wow.. thanks you saved my life!:cool:

Works! Created a file in /etc/modprobe.d called kvm_amd.conf with just this line in it:

blacklist kvm_amd

Rebooted, checked lsmod, and the kvm and kvm_amd modules were gone.
Do the same, but with kvm_intel, and you should be OK

Modprobe :oh god : At last a solution !

Hi everybody !

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