FS#41375 - [virtualbox-host-modules] vboxdrv disagrees about version of symbol module_layout with 3.15.7-1-ARCH

Attached to Project: Community Packages
Opened by Christopher Schmidt (archlinux20130905) - Tuesday, 29 July 2014, 06:11 GMT
Last edited by Doug Newgard (Scimmia) - Tuesday, 29 July 2014, 17:20 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sébastien Luttringer (seblu)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 5
Private No

Details

Description:

I just updated my kernel to 3.15.7-1-ARCH and Virtualbox 4.3.14-1 stopped working.

Additional info:
Here is the relevant information as shown by 'journalctl -b':

[..]
systemd-modules-load[103]: Failed to insert 'vboxdrv': Exec format error
kernel: vboxdrv: disagrees about version of symbol module_layout
[..]

A similar error message is shown for vboxnetadp, vboxnetflt and vboxpci: Exec format error. Note that this error message is very similar to the current nvidia-driver-problem related to this particular kernel-update. So maybe other modules other than virtualbox and nvidia could be affected as well? Even though no additional errors are shown in my journalctl-log.

Steps to reproduce:
Install the currently newest virtualbox 4.3.14-1 from the official repositories on a 32-bit system running the currently newest Archlinux kernel 3.15.7-1.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Tuesday, 29 July 2014, 17:20 GMT
Reason for closing:  Fixed
Additional comments about closing:  4.3.14-3
Comment by Christopher Schmidt (archlinux20130905) - Tuesday, 29 July 2014, 07:33 GMT
quote:

"Note that this error message is very similar to the current nvidia-driver-problem related to this particular kernel-update."

I mean this one: https://bugs.archlinux.org/task/41373
Comment by Eugenio M. Vigo (emvigo) - Tuesday, 29 July 2014, 08:46 GMT
I can confirm this bug. For instance, this is what happens when you want to modprobe the module.

[ugi@UGI ~]$ sudo modprobe vboxdrv
modprobe: ERROR: could not insert 'vboxdrv': Exec format error
Comment by Kenneth Brown (kenneththomasbrown) - Tuesday, 29 July 2014, 17:09 GMT
You can work around this issue by building the driver yourself against the new kernel headers.

Example:
$ sudo pacman -S abs
$ sudo abs
$ cp -r /var/abs/community/virtualbox-host-modules ~/
$ cd ~/virtualbox-host-modules
$ makepkg -csi

Loading...