[SOLVED] Virtualbox with -ck kernel: ERROR: could not insert 'vboxdrv'

edmael · 2012-08-06 16:19:17

Hi everyone,
I want to install Virtuabox on Arch and I am running a -ck kernel. I followed the instruction on the wiki and installed the following packages:

virtualbox-4.1.18-4  virtualbox-additions-4.1.18-1  virtualbox-archlinux-additions-4.1.18-4  virtualbox-archlinux-modules-4.1.18-4 virtualbox-archlinux-source-4.1.18-4  virtualbox-modules-4.1.18-4  virtualbox-source-4.1.18-4

Then I run:

dkms install vboxhost/4.1.18 -k 3.4.7-1-ck/x86_64

and I get this output:

brain edu # dkms install vboxhost/4.1.18 -k 3.4.7-1-ck/x86_64

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area....
make KERNELRELEASE=3.4.7-1-ck -C /usr/lib/modules/3.4.7-1-ck/build M=/var/lib/dkms/vboxhost/4.1.18/build..................
cleaning build area....

DKMS: build completed.

vboxdrv.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /usr/lib/modules/3.4.7-1-ck/kernel/misc/

vboxnetflt.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /usr/lib/modules/3.4.7-1-ck/kernel/misc/

vboxnetadp.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /usr/lib/modules/3.4.7-1-ck/kernel/misc/

vboxpci.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /usr/lib/modules/3.4.7-1-ck/kernel/misc/

depmod..............

DKMS: install completed.

So i try to load vboxdrv with:

modprobe vboxdrv

But I get this error:

ERROR: could not insert 'vboxdrv': Exec format error

Can someone told me how to fix this?
I read somewhere here on the forum to delete the files in /usr/lib/extramodules, but I don't have that folder.

Thanks!

Last edited by edmael (2012-08-08 13:54:43)

graysky · 2012-08-06 19:56:39

Yeah, this dkms stuff is a real pain in the balls. Do you have the corresponding linux-ck-headers package installed? Here's what I did:

# pacman -S virtualbox virtualbox-source
# dkms install vboxhost/4.1.18

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
.
make KERNELRELEASE=3.5.0-1-ck -C /usr/lib/modules/3.5.0-1-ck/build M=/var/lib/dkms/vboxhost/4.1.18/build........
cleaning build area....

DKMS: build completed.

vboxdrv.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /usr/lib/modules/3.5.0-1-ck/kernel/misc/

vboxnetflt.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /usr/lib/modules/3.5.0-1-ck/kernel/misc/

vboxnetadp.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /usr/lib/modules/3.5.0-1-ck/kernel/misc/

vboxpci.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /usr/lib/modules/3.5.0-1-ck/kernel/misc/

depmod....

DKMS: install completed.

Last edited by graysky (2012-08-06 19:58:38)

edmael · 2012-08-06 20:28:05

Thanks for the reply!
But, yes, the headers are installed correctly.
I'll try to remove everything and then reinstall.

EDIT: did the same thing you did, but I get the same error as before.

Last edited by edmael (2012-08-06 20:32:04)

graysky · 2012-08-06 23:32:04

@edmael - I just updated the linux-ck package's provides array for the headers-package. If you're using the repo, you'll have to wait an hour or so for the rebuild. If using the AUR, download 3.4.7-2 and compile. Then report back please.

Note - if you remove the virtualbox package, you must re-add your users to the vboxusers group as the uninstall pulls all users from it!

# gpasswd -a YOURUSER vboxusers

Last edited by graysky (2012-08-06 23:33:29)

litemotiv · 2012-08-07 08:23:35

Be sure to manually remove any old kernel modules that were created with vboxbuild, modprobe might be trying to insert the wrong module.

edmael · 2012-08-07 14:49:54

So, let me retry.

pacman -R virtualbox virtualbox-source

pacman -S virtualbox virtualbox-source linux-ck-corex-header

(linux-ck-corex-header was already installed)
Then:

brain Documenti # gpasswd -a edu vboxusers 
Aggiunta dell'utente edu al gruppo vboxusers
brain Documenti # dkms install vboxhost/4.1.18

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area....
make KERNELRELEASE=3.4.7-2-ck -C /usr/lib/modules/3.4.7-2-ck/build M=/var/lib/dkms/vboxhost/4.1.18/build................
cleaning build area....

DKMS: build completed.

vboxdrv.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /usr/lib/modules/3.4.7-2-ck/kernel/misc/

vboxnetflt.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /usr/lib/modules/3.4.7-2-ck/kernel/misc/

vboxnetadp.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /usr/lib/modules/3.4.7-2-ck/kernel/misc/

vboxpci.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /usr/lib/modules/3.4.7-2-ck/kernel/misc/

depmod..............

DKMS: install completed.

So I try with:

brain Documenti # modprobe vboxdrv
ERROR: could not insert 'vboxdrv': Exec format error

Same error.

litemotiv, how can I remove any old kernel modules?
If I try with:

brain Documenti # modprobe -r 
ac                     ehci_hcd               joydev                 processor              snd_hwdep              usbhid
acer_wmi               evdev                  libahci                psmouse                snd_page_alloc         uvcvideo
acpi_cpufreq           ext4                   libata                 rfkill                 snd_pcm                uvesafb
ahci                   hid                    libphy                 scsi_mod               snd_timer              video
arc4                   i2c_core               mac80211               sd_mod                 soundcore              videobuf2_core
autofs4                i2c_i801               mbcache                serio_raw              sparse_keymap          videobuf2_memops
battery                intel_agp              media                  sg                     sr_mod                 videobuf2_vmalloc
button                 intel_gtt              microcode              snd                    tg3                    videodev
cdrom                  iTCO_vendor_support    mperf                  snd_hda_codec          thermal                wmi
cfg80211               iTCO_wdt               mxm_wmi                snd_hda_codec_hdmi     uhci_hcd               
coretemp               iwlwifi                nvidia                 snd_hda_codec_realtek  usb_common             
crc16                  jbd2                   pcspkr                 snd_hda_intel          usbcore

I don't see any Virtualbox module.

Other thing I might try?

litemotiv · 2012-08-07 15:53:24

Edmael, have a look in /usr/lib/modules/ for any stray modules from earlier builds

edmael · 2012-08-07 17:16:06

Hum... Interesting...

edu@brain /usr/lib/modules $ ls -la
totale 176
drwxr-xr-x   7 root root   4096  7 ago 14.29 .
drwxr-xr-x 184 root root 151552  7 ago 16.45 ..
drwxr-xr-x   3 root root   4096  7 ago 00.20 3.4.7-1-ARCH
drwxr-xr-x   3 root root   4096  7 ago 16.44 3.4.7-1-ck
drwxr-xr-x   3 root root   4096  7 ago 16.48 3.4.7-2-ck
drwxr-xr-x   2 root root   4096  7 ago 00.20 extramodules-3.4-ARCH
drwxr-xr-x   2 root root   4096  7 ago 14.29 extramodules-3.4-ck

So, assuming that I'm using the kernel 3.4.7-2-ck I can safely delete those extramodules and try to rebuild them with dkms, right?

EDIT:
That's not correct.
Inside the extramodules-3.4-ck I found:

nvidia.ko.gz  vboxdrv.ko.gz  vboxnetadp.ko.gz  vboxnetflt.ko.gz  vboxpci.ko.gz  version

Now I'll try to remove vboxdrv.ko.gz and rebuild it.

EDIT2:
D'oh!

brain extramodules-3.4-ck # dkms install vboxhost/4.1.18
Module vboxhost/4.1.18 already installed on kernel 3.4.7-2-ck/x86_64

Just found out that also 3.4.7-2-ck have an /extramodules folder in it, but no sign of vboxdrv...

Last edited by edmael (2012-08-07 17:22:54)

litemotiv · 2012-08-07 18:47:13

You can use the --verbose switch to see which module is probed:

# modprobe --verbose vboxdrv
insmod /usr/lib/modules/3.4.7-2-ck/kernel/misc/vboxdrv.ko

graysky · 2012-08-07 19:30:07

Man, now I am experiencing this problem.

# ls -l /usr/lib/modules/3.5.0-1-ck/kernel/misc/
total 2044
-rw-r--r-- 1 root root 2002808 Aug  7 15:28 vboxdrv.ko
-rw-r--r-- 1 root root   14496 Aug  7 15:28 vboxnetadp.ko
-rw-r--r-- 1 root root   36720 Aug  7 15:28 vboxnetflt.ko
-rw-r--r-- 1 root root   36520 Aug  7 15:28 vboxpci.ko

But...

# modprobe --verbose vboxdrv
insmod /usr/lib/modules/3.5.0-1-ck/kernel/misc/vboxdrv.ko 
ERROR: could not insert 'vboxdrv': Exec format error

WTF?

graysky · 2012-08-07 19:45:19

OK... after a removal and rebuild it's fine... something is wrong with dkms I think.

# pacman -Rs virtualbox-source virtualbox
# pacman -S virtualbox virtualbox-source

# dkms install vboxhost/4.1.18

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area....
make KERNELRELEASE=3.5.0-1-ck -C /usr/lib/modules/3.5.0-1-ck/build M=/var/lib/dkms/vboxhost/4.1.18/build........
cleaning build area....

DKMS: build completed.

vboxdrv.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /usr/lib/modules/3.5.0-1-ck/kernel/misc/

vboxnetflt.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /usr/lib/modules/3.5.0-1-ck/kernel/misc/

vboxnetadp.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /usr/lib/modules/3.5.0-1-ck/kernel/misc/

vboxpci.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /usr/lib/modules/3.5.0-1-ck/kernel/misc/

depmod....

DKMS: install completed.

# gpasswd -a facade vboxusers
# /etc/rc.d/dkms start
:: Starting Dynamic Kernel Module System                                                                 [DONE]

# ls -l /usr/lib/modules/3.5.0-1-ck/kernel/misc
total 2044
-rw-r--r-- 1 root root 2002808 Aug  7 15:37 vboxdrv.ko
-rw-r--r-- 1 root root   14496 Aug  7 15:37 vboxnetadp.ko
-rw-r--r-- 1 root root   36720 Aug  7 15:37 vboxnetflt.ko
-rw-r--r-- 1 root root   36520 Aug  7 15:37 vboxpci.ko

Last edited by graysky (2012-08-07 19:45:42)

edmael · 2012-08-07 20:09:23

Thanks, I'll try again...
At least, I'm not alone!

EDIT:
Aw, come on!

brain ~ # /etc/rc.d/dkms start
:: Starting Dynamic Kernel Module System                                                        [BUSY]
ERROR: could not insert 'vboxnetadp': Exec format error
ERROR: could not insert 'vboxnetflt': Exec format error
ERROR: could not insert 'vboxpci': Exec format error
                                                                                                                               [DONE]

Wait, Virtualbox is working and modprobe vboxdrv works too!

Last edited by edmael (2012-08-07 20:24:59)

graysky · 2012-08-07 20:52:31

Glad to hear that but what is the source of this problem?

edmael · 2012-08-07 21:10:12

I don't know.
And the network on my VM won't work, keeps give an error about the setup of vboxdrv.
But without the network the WM works just fine!

litemotiv · 2012-08-08 08:49:12

My guess would be that you also have older versions of the other modules dormant on your system..

khampf · 2012-08-08 12:44:06

I had to get rid of:
./extramodules-3.4-ck/vboxnetadp.ko.gz
./extramodules-3.4-ck/vboxpci.ko.gz
./extramodules-3.4-ck/vboxnetflt.ko.gz
./extramodules-3.4-ck/vboxdrv.ko.gz

Rebuilt using dkms install and now it works!

$ sudo dkms install vboxhost/4.1.18
[ ... blahblah ... ]
DKMS: install completed.

$ find /lib/modules -name 'vbox*' -exec pacman -Qo {} +
/lib/modules/extramodules-3.4-ARCH/vboxnetadp.ko.gz is owned by virtualbox-modules 4.1.18-4
/lib/modules/extramodules-3.4-ARCH/vboxpci.ko.gz is owned by virtualbox-modules 4.1.18-4
/lib/modules/extramodules-3.4-ARCH/vboxnetflt.ko.gz is owned by virtualbox-modules 4.1.18-4
/lib/modules/extramodules-3.4-ARCH/vboxdrv.ko.gz is owned by virtualbox-modules 4.1.18-4
error: No package owns /lib/modules/3.4.7-2-ck/kernel/misc/vboxnetflt.ko
error: No package owns /lib/modules/3.4.7-2-ck/kernel/misc/vboxnetadp.ko
error: No package owns /lib/modules/3.4.7-2-ck/kernel/misc/vboxpci.ko
error: No package owns /lib/modules/3.4.7-2-ck/kernel/misc/vboxdrv.ko

(the unowned modules are managed by dkms so they shouldn't be owned by any packages)

Last edited by khampf (2012-08-08 12:47:12)

edmael · 2012-08-08 13:15:02

Removing the modules and rebuilding them with dkms worked!
Thanks!

msx · 2012-08-15 07:48:18

Just for the record, this very same procedure applies to linux-lqx (Liquorix) kernel and I presume to every-other non-stock kernel.

graysky · 2012-08-17 23:50:03

So this isn't solved. I updated my system to 3.5.2-1 and am running into the same problem here with the solution NOT working.

$ sudo dkms uninstall vboxhost/4.1.18
...

$ find /lib/modules -name 'vbox*' -exec pacman -Qo {} +
$ sudo dkms install vboxhost/4.1.18
...


$ find /lib/modules -name 'vbox*' -exec pacman -Qo {} +
error: No package owns /lib/modules/3.5.2-1-ck/kernel/misc/vboxnetflt.ko
error: No package owns /lib/modules/3.5.2-1-ck/kernel/misc/vboxpci.ko
error: No package owns /lib/modules/3.5.2-1-ck/kernel/misc/vboxdrv.ko
error: No package owns /lib/modules/3.5.2-1-ck/kernel/misc/vboxnetadp.ko

$ sudo modprobe vboxnetflt
ERROR: could not insert 'vboxnetflt': Exec format error

Has anyone else run into this after upgrading from 3.4.x to 3.5.2-ck?

EDIT: OK... seems as though it DOES work if you first remove the virtualbox virtualbox-source packages and then run the dkms install command.

The difference is this:

$ sudo dkms install vboxhost/4.1.18

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area....
make KERNELRELEASE=3.5.2-1-ck -C /usr/lib/modules/3.5.2-1-ck/build M=/var/lib/dkms/vboxhost/4.1.18/build........
cleaning build area....

DKMS: build completed.
...

EDIT: If one runs the dkms install command without first removing the packages that "cleaning build area" step is omitted!

Opened bug report - https://bugs.archlinux.org/task/31180

Last edited by graysky (2012-08-18 00:05:54)

litemotiv · 2012-08-18 09:26:04

@graysky: i didn't have to do that here;

- Upgrade to 3.5.2-ck
- Issue dkms install vboxhost/4.1.18

# dkms install vboxhost/4.1.18

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area....
make KERNELRELEASE=3.5.2-1-ck -C /usr/lib/modules/3.5.2-1-ck/build M=/var/lib/dkms/vboxhost/4.1.18/build............
cleaning build area....

DKMS: build completed.

vboxdrv.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /usr/lib/modules/3.5.2-1-ck/kernel/misc/

   - No original module exists within this kernel
 - Installation
   - Installing to /usr/lib/modules/3.5.2-1-ck/kernel/misc/

vboxnetflt.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /usr/lib/modules/3.5.2-1-ck/kernel/misc/

vboxnetadp.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /usr/lib/modules/3.5.2-1-ck/kernel/misc/

vboxpci.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /usr/lib/modules/3.5.2-1-ck/kernel/misc/

depmod.....

- Modprobe vboxdrv
- Start VirtualBox

Edit: the difference being that i didn't run dkms uninstall

Last edited by litemotiv (2012-08-18 09:27:35)

graysky · 2012-08-18 10:45:58

@lm - no idea what is wrong on my box then. However, if you look at the output of your dkms install step, it omits the cleaning build area bit that was critical to the success on my system. Plus, it is my understanding the dkms should rebuild these modules automatically when the kernel is updated, no? Why do we need to issue a rebuild command for dkms at all? Are we missing some key config hook?

Last edited by graysky (2012-08-18 10:46:53)

msx · 2012-08-18 21:12:50

@graysky: may be you are missing this?

Extracted from our VirtualBox Wiki:
[...]Automatic re-compilation of the virtualbox modules with every kernel update
Note: The hook has been updated to run dkms (not as a daemon) instead of vboxbuild.
This is possible thanks to virtualbox-hook from the AUR. In virtualbox-hook, the 'automatic re-compilation' functionality is done by a vbox hook on mkinitcpio after forcing to update the linux-headers package. You will need to add 'vbox' to the HOOKS array in /etc/mkinitcpio.conf as well as 'linux-headers' and your custom kernel(s) headers to the SyncFirst array in /etc/pacman.conf for this to work.
The hook will call the dkms command to update the virtualbox modules for the version of your new kernel.[...]"

azbarcea · 2015-08-15 17:10:42

I had the same problem, but the reason was, because I had multiple pacman repos (test and non-test).

I had to:
* remove vbox related packages
* remove the compiled vbox modules from /lib/modules/<my-kernel>/extramodules/vbox*
* disable the community-testing repo
* install virtualbox
* modprobe vboxdrv
* done

Trilby · 2015-08-15 18:07:15

Welcome to the forums azbarcea. Please have a look at our forum guidelines, and avoid "necrobumping" old threads - especially solved ones.

Closed.

Arch Linux

#1 2012-08-06 16:19:17

[SOLVED] Virtualbox with -ck kernel: ERROR: could not insert 'vboxdrv'

#2 2012-08-06 19:56:39

Re: [SOLVED] Virtualbox with -ck kernel: ERROR: could not insert 'vboxdrv'

#3 2012-08-06 20:28:05

Re: [SOLVED] Virtualbox with -ck kernel: ERROR: could not insert 'vboxdrv'

#4 2012-08-06 23:32:04

Re: [SOLVED] Virtualbox with -ck kernel: ERROR: could not insert 'vboxdrv'

#5 2012-08-07 08:23:35

Re: [SOLVED] Virtualbox with -ck kernel: ERROR: could not insert 'vboxdrv'

#6 2012-08-07 14:49:54

Re: [SOLVED] Virtualbox with -ck kernel: ERROR: could not insert 'vboxdrv'

#7 2012-08-07 15:53:24

Re: [SOLVED] Virtualbox with -ck kernel: ERROR: could not insert 'vboxdrv'

#8 2012-08-07 17:16:06

Re: [SOLVED] Virtualbox with -ck kernel: ERROR: could not insert 'vboxdrv'

#9 2012-08-07 18:47:13

Re: [SOLVED] Virtualbox with -ck kernel: ERROR: could not insert 'vboxdrv'

#10 2012-08-07 19:30:07

Re: [SOLVED] Virtualbox with -ck kernel: ERROR: could not insert 'vboxdrv'

#11 2012-08-07 19:45:19

Re: [SOLVED] Virtualbox with -ck kernel: ERROR: could not insert 'vboxdrv'

#12 2012-08-07 20:09:23

Re: [SOLVED] Virtualbox with -ck kernel: ERROR: could not insert 'vboxdrv'

#13 2012-08-07 20:52:31

Re: [SOLVED] Virtualbox with -ck kernel: ERROR: could not insert 'vboxdrv'

#14 2012-08-07 21:10:12

Re: [SOLVED] Virtualbox with -ck kernel: ERROR: could not insert 'vboxdrv'

#15 2012-08-08 08:49:12

Re: [SOLVED] Virtualbox with -ck kernel: ERROR: could not insert 'vboxdrv'

#16 2012-08-08 12:44:06

Re: [SOLVED] Virtualbox with -ck kernel: ERROR: could not insert 'vboxdrv'

#17 2012-08-08 13:15:02

Re: [SOLVED] Virtualbox with -ck kernel: ERROR: could not insert 'vboxdrv'

#18 2012-08-15 07:48:18

Re: [SOLVED] Virtualbox with -ck kernel: ERROR: could not insert 'vboxdrv'

#19 2012-08-17 23:50:03

Re: [SOLVED] Virtualbox with -ck kernel: ERROR: could not insert 'vboxdrv'

#20 2012-08-18 09:26:04

Re: [SOLVED] Virtualbox with -ck kernel: ERROR: could not insert 'vboxdrv'

#21 2012-08-18 10:45:58

Re: [SOLVED] Virtualbox with -ck kernel: ERROR: could not insert 'vboxdrv'

#22 2012-08-18 21:12:50

Re: [SOLVED] Virtualbox with -ck kernel: ERROR: could not insert 'vboxdrv'

#23 2015-08-15 17:10:42

Re: [SOLVED] Virtualbox with -ck kernel: ERROR: could not insert 'vboxdrv'

#24 2015-08-15 18:07:15

Re: [SOLVED] Virtualbox with -ck kernel: ERROR: could not insert 'vboxdrv'

Board footer