Arch Linux

Sublime2k

Member

Registered: 2014-03-17

Posts: 46

[SOLVED] VirtualBox broken after last update, problem with vboxdrv

I updated my system yesterday, I'm running kernel 3.15.7-1-ARCH.

I just found out that VirtualBox doesn't work any more. I can run VirtualBox itself, but there seems to be a problem with vboxdrv when I try to run my virtual machine running Windows 7.

Here are the 2 erros I get:

VirtualBox - Error

Failed to open a session for the virtual machine Windows.

The virtual machine 'Windows' has terminated unexpectedly during startup with exit code 1.

Details:

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

VirtualBox - Error In suplibOsInit

Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver (xvboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing

'pacman -S virtualbox-host-modules'

as root. If you don't use our stock kernel, install virtualbox-host-dkms and execute dkms autoinstall.

I have tried reinstalling virtualbox-host-modules and it didn't help. Reinstalling virtualbox package itself didn't help either.

I already have vboxdrv in /etc/modules-load.d/virtualbox.conf. Running modprobe vboxdrv as root gives me this error:

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

And lastly, /dev/vboxdrv doesn't even exist (I'm not sure if it existed in first place or latest update deleted it).

Any ideas how to fix this?

Thanks in advance.

Last edited by Sublime2k (2014-07-29 13:56:51)

ploub

Member

Registered: 2007-05-16

Posts: 132

Re: [SOLVED] VirtualBox broken after last update, problem with vboxdrv

See this topic - it's been covered already

Sublime2k

Member

Registered: 2014-03-17

Posts: 46

Re: [SOLVED] VirtualBox broken after last update, problem with vboxdrv

See this topic - it's been covered already

It didn't show up when I searched for it, weird.

Anyway, the only solutions proposed in that topic are rebooting and running depmod -a which didn't help me.

olsman037

Member

Registered: 2011-06-17

Posts: 27

Re: [SOLVED] VirtualBox broken after last update, problem with vboxdrv

Solved by updating virtualbox-host-modules…

halogene

Member

Registered: 2013-05-29

Posts: 47

Re: [SOLVED] VirtualBox broken after last update, problem with vboxdrv

Not for me - I even uninstalled virtualbox completely, checked that there was no vboxdrv module present anymore, and reinstalled, still I get

insmod /lib/modules/3.15.7-1-ARCH/extramodules/vboxdrv.ko.gz 
modprobe: ERROR: could not insert 'vboxdrv': Exec format error

Edit: oh, and I did depmod -a both after uninstall and reinstall.

Last edited by halogene (2014-07-29 10:41:31)

halogene

Member

Registered: 2013-05-29

Posts: 47

Re: [SOLVED] VirtualBox broken after last update, problem with vboxdrv

Update: maybe my mirror was a bit slower in updating than yours. A second update came in for the virtualbox modules, and after upgrading to virtualbox-host-modules-4.3.14-3, the problem was solved indeed.

Last edited by halogene (2014-07-29 12:27:12)

Sublime2k

Member

Registered: 2014-03-17

Posts: 46

Re: [SOLVED] VirtualBox broken after last update, problem with vboxdrv

Update: maybe my mirror was a bit slower in updating than yours. A second update came in for the virtualbox modules, and after upgrading to virtualbox-host-modules-4.3.14-3, the problem was solved indeed.

Likewise.

After updating virtualbox-host-modules from 4.3.14-1 to 4.3.14-3 today, VirtualBox seems to be working fine.

Another (temporary) solution is to downgrade the kernel to the last one that was working using this command:

pacman -U /var/cache/pacman/pkg/linux-3.15.5-2-x86_64.pkg.tar.xz

xpander

Member

Registered: 2013-01-23

Posts: 56

Re: [SOLVED] VirtualBox broken after last update, problem with vboxdrv

what i did to get it working:

sudo pacman -S abs

sudo abs community/virtualbox-modules

then ran makepkg -si on the virtualbox-modules directory (copied it from  /var/abs/community/ to a place where i have permissions)

then ran sudo modprobe vboxdrv vboxnetadp vboxnetflt vboxpci

and all works well now

its cause my mirrors still have 4.3.14-1

Last edited by xpander (2014-07-29 14:46:00)

---

Linux Gaming Videos:http://www.youtube.com/user/Xpander666

Sublime2k

Member

Registered: 2014-03-17

Posts: 46

Re: [SOLVED] VirtualBox broken after last update, problem with vboxdrv

its cause my mirrors still have 4.3.14-1

Speaking of which... Why does that happen? If pacman -Syy doesn't help, is there a way to "force" the mirrors to update? Shouldn't they update for everyone at the same time?

Last edited by Sublime2k (2014-07-29 14:57:36)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 11,543

Re: [SOLVED] VirtualBox broken after last update, problem with vboxdrv

Mirrors all sync on their own schedule. xpander's mirror simply hasn't updated itself yet.

olsman037

Member

Registered: 2011-06-17

Posts: 27

Re: [SOLVED] VirtualBox broken after last update, problem with vboxdrv

@Sublime2k
To force updating mirrors (or force using more up to date mirrors) you can use reflector. I use an alias to do it.

sudo reflector -l 8 --sort delay --sort rate --sort age --protocol http --protocol ftp --country France --country Belgium --country Great\ Britain --country Germany --save /etc/pacman.d/mirrorlist && yaourt -Syyua'

Check the wiki to adapt this command.

meltfund

Member

Registered: 2014-10-12

Posts: 1

Re: [SOLVED] VirtualBox broken after last update, problem with vboxdrv

I'm still getting it.

Tried all the fixes above: reinstall, depmod -a, using up to date mirrors

[root@desktop ~]# modprobe -v vboxdrv
insmod /lib/modules/3.16.3-1-ARCH/extramodules/vboxdrv.ko.gz
modprobe: ERROR: could not insert 'vboxdrv': Exec format error
[root@desktop ~]#

Has it come back somehow?

Scimmia

Fellow

Registered: 2012-09-01

Posts: 11,543

Re: [SOLVED] VirtualBox broken after last update, problem with vboxdrv

meltfund:
First, don't necrobump.
Second, partial updates are not supported. Did you update the modules without updating the kernel?