[SOLVED] VirtualBox modules don't load after upgrade to kernel 4.4.3-1

ninian · 2016-03-03 17:53:25

Did a 'pacman -Syu' on two standard 64-bit Arch systems with previously working VirtualBox installations. Kernel upgraded to: linux 4.4.3-1
(Once system had DKMS installed, the other did not.)
Now the vboxdrv module fails to load, both at boot and manually trying to load it with modprobe.
Here's what the journal reports:

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

It's a while since I've used VirtualBox in earnest, so excuse me if I'm missing something obvious.

Last edited by ninian (2016-03-05 01:04:26)

IMBJR · 2016-03-03 18:51:08

I'm seeing this too. In my journal I see:

Failed to start Load Kernel Modules

then later on:

Failed to insert 'vboxdrv': Exec format error
Failed to insert 'vboxvideo': Exec format error
Failed to insert 'vboxnetflt': Exec format error

And that's after a manual rebuild.

IMBJR · 2016-03-03 19:40:41

Well, hopefully, this is because virtualbox-host-modules is out of date.

ninian · 2016-03-03 19:52:31

IMBJR wrote:

Well, hopefully, this is because virtualbox-host-modules is out of date.

Am surprised more people haven't been reporting this problem, if it's something as gross as that.
Here's hoping ...

jz_train · 2016-03-03 19:55:30

Some guys on the IRC channel figured it out. I didn't catch their workaround. I was busy downgrading the kernel so I missed it. Anybody here find a fix?

voepew · 2016-03-03 19:58:30

Yes, after kernel upgrade it's unusable.. Looking for the fix.

jz_train · 2016-03-03 20:09:42

OK, so download this and build the pkgbuild for your architecture.

https://projects.archlinux.org/svntogit … les.tar.gz

Modprobe the modules and you'll be good to go. Thanks to @sw1f7 on #archlinux IRC

koc · 2016-03-03 20:22:50

Or temporarily downgrade kernel:

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

snowhog · 2016-03-03 20:35:52

This kernel update killed my Arch VM (Oracle VirtualBox). And using the fallback img doesn't work either. I'm presented with the following using either:

"Welcome to emergency mode! After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to try again to boot into default mode. Give root password for maintenance (or press Control-D to continue):"

^D doesn't work; I have to login using my root account password, and then I have no working wireless connection (did before this fiasco) and I don't have a wired connection I can use. Tried configuring /etc/netctl as per my installation notes (which worked with the installation). Nada. Tried using wifi-menu. Nada: I'm informed that I have to install dialog, which was already installed during the installation.

So I now have no working network, so can't perform any package maintenance. The fallback img doesn't work. I have a borked Arch in my VM. Nice.

So, unless someone is willing to do some hand holding with me to see if there is anything I can do to get a functional network connection, I'm going to have to erase the VM and start all over, and not allow the upgraded kernel to be installed.

Update:
Fixed my problem by re-installing the prior downloaded kernel: sudo pacman -U /var/cache/pacman/pkg/linux-4.4.1-1-i686.pkg.tar.xz

Rebooted the VM and all is back as it should be.

Last edited by snowhog (2016-03-03 21:34:50)

d3lph1 · 2016-03-03 20:39:05

I have the same trouble (modprobe/systemd failures)! Looking forward for upgrade in the upstream.

Last edited by d3lph1 (2016-03-03 20:40:11)

kwash · 2016-03-03 21:50:01

Same here: virtualbox brakes after new kernel 4.4.3 update.

Waiting for the fix to hit the official repositories.

Last edited by kwash (2016-03-03 21:50:15)

bulletmark · 2016-03-03 21:55:58

ninian wrote:

IMBJR wrote:
Well, hopefully, this is because virtualbox-host-modules is out of date.
Am surprised more people haven't been reporting this problem, if it's something as gross as that.

It does appear to be that simple. Just bit me also.

yndoendo · 2016-03-03 22:46:40

This issue is only occurring on my AMD desktop. Kernel modules loaded just fine on my INTEL laptop.

SDR · 2016-03-03 23:26:18

This seems to be an issue with KDE as well. Devs are aiming to appease mobile platforms, thrashing on their way the desktops.

No proper solution, yet?

ninian · 2016-03-03 23:43:38

yndoendo wrote:

This issue is only occurring on my AMD desktop. Kernel modules loaded just fine on my INTEL laptop.

Mine are both Intel systems.

cdown · 2016-03-04 01:18:06

Downgrading the kernel seems a bad idea, since it will likely cause other issues once other modules are upgraded to support 4.4.3. Partial upgrades aren't supported, and this is a particularly likely one to go wrong.

Better would be to rebuild virtualbox-guest-modules from ABS. I've written up instructions about how to do this here:

https://chrisdown.name/2016/03/03/virtu … o-443.html

Last edited by cdown (2016-03-04 01:59:36)

cdown · 2016-03-04 01:20:34

Looks like the package is orphaned too -- despite being a "community" package, this is pretty critical for a large number of users, so I'm surprised that it's got to this state.

kwash · 2016-03-04 02:14:23

cdown wrote:

Downgrading the kernel seems a bad idea, since it will likely cause other issues once other modules are upgraded to support 4.4.3. Partial upgrades aren't supported, and this is a particularly likely one to go wrong.

I can confirm this. After a downgrade to kernel 4.4.1 the boot hangs. Using Intel system with Plasma desktop.

After reinstalling kernel 4.4.3 the boot was normal again.

I prefer to wait for the official repository fix.

Last edited by kwash (2016-03-04 02:27:07)

cdown · 2016-03-04 02:30:12

kwash wrote:

cdown wrote:
Downgrading the kernel seems a bad idea, since it will likely cause other issues once other modules are upgraded to support 4.4.3. Partial upgrades aren't supported, and this is a particularly likely one to go wrong.
I can confirm this. After a downgrade to kernel 4.4.1 the boot hangs. Using Intel system with Plasma desktop.
After reinstalling kernel 4.4.3 the boot was normal again.
I prefer to wait for the official repository fix.

Like I said, rebuilding virtualbox-modules from ABS should be fine. I've put up instructions here: https://chrisdown.name/2016/03/03/virtu … o-443.html :-)

kwash · 2016-03-04 02:38:55

cdown wrote:

Like I said, rebuilding virtualbox-modules from ABS should be fine. I've put up instructions here: https://chrisdown.name/2016/03/03/virtu … o-443.html :-)

Thank you cdown.

Nice post on your website by the way.

ronw · 2016-03-04 04:46:44

Just got an upgrade, virtualbox-host-modules (5.0.14-3 -> 5.0.14-4), reloaded the modules, and VMs are working.

SDR · 2016-03-04 05:27:47

Intel4790&KDE had no problem downgrading to Linux arch64 4.4.1-2-ARCH #1 SMP PREEMPT Wed Feb 3 13:12:33 UTC 2016 x86_64 GNU/Linux
but the rebuild of vbox-host .. was no luck at all

Last edited by SDR (2016-03-04 05:29:16)

macstar3000 · 2016-03-04 05:59:29

more than vbox modules here. system won't reboot anymore >> http://www.imgus.net/i/d9bb5094b16ce103 … 55e981.jpg

lucky that i am on linux-ck as default kernel, which is working just fine.

please, ignore my posting i discovered nvidia package was not installed anymore and this was the reason the system would not boot up. everything fine now.

Last edited by macstar3000 (2016-03-04 09:41:43)

ninian · 2016-03-04 08:43:10

ronw wrote:

Just got an upgrade, virtualbox-host-modules (5.0.14-3 -> 5.0.14-4), reloaded the modules, and VMs are working.

Works for me too now (at least on the one system I've tried so far).

Angelsoul · 2016-03-04 18:58:25

ninian wrote:

ronw wrote:
Just got an upgrade, virtualbox-host-modules (5.0.14-3 -> 5.0.14-4), reloaded the modules, and VMs are working.
Works for me too now (at least on the one system I've tried so far).

Yes, the upgrade works for me too.

I installed the newest package from https://www.archlinux.org/packages/comm … t-modules/.
But in community I still have the previous one. I mean, even if i do pcamn -Syy, I still have the 5.014-3 version in the community db.
Can somebody tell me why?

Arch Linux

#1 2016-03-03 17:53:25

[SOLVED] VirtualBox modules don't load after upgrade to kernel 4.4.3-1

#2 2016-03-03 18:51:08

Re: [SOLVED] VirtualBox modules don't load after upgrade to kernel 4.4.3-1

#3 2016-03-03 19:40:41

Re: [SOLVED] VirtualBox modules don't load after upgrade to kernel 4.4.3-1

#4 2016-03-03 19:52:31

Re: [SOLVED] VirtualBox modules don't load after upgrade to kernel 4.4.3-1

#5 2016-03-03 19:55:30

Re: [SOLVED] VirtualBox modules don't load after upgrade to kernel 4.4.3-1

#6 2016-03-03 19:58:30

Re: [SOLVED] VirtualBox modules don't load after upgrade to kernel 4.4.3-1

#7 2016-03-03 20:09:42

Re: [SOLVED] VirtualBox modules don't load after upgrade to kernel 4.4.3-1

#8 2016-03-03 20:22:50

Re: [SOLVED] VirtualBox modules don't load after upgrade to kernel 4.4.3-1

#9 2016-03-03 20:35:52

Re: [SOLVED] VirtualBox modules don't load after upgrade to kernel 4.4.3-1

#10 2016-03-03 20:39:05

Re: [SOLVED] VirtualBox modules don't load after upgrade to kernel 4.4.3-1

#11 2016-03-03 21:50:01

Re: [SOLVED] VirtualBox modules don't load after upgrade to kernel 4.4.3-1

#12 2016-03-03 21:55:58

Re: [SOLVED] VirtualBox modules don't load after upgrade to kernel 4.4.3-1

#13 2016-03-03 22:46:40

Re: [SOLVED] VirtualBox modules don't load after upgrade to kernel 4.4.3-1

#14 2016-03-03 23:26:18

Re: [SOLVED] VirtualBox modules don't load after upgrade to kernel 4.4.3-1

#15 2016-03-03 23:43:38

Re: [SOLVED] VirtualBox modules don't load after upgrade to kernel 4.4.3-1

#16 2016-03-04 01:18:06

Re: [SOLVED] VirtualBox modules don't load after upgrade to kernel 4.4.3-1

#17 2016-03-04 01:20:34

Re: [SOLVED] VirtualBox modules don't load after upgrade to kernel 4.4.3-1

#18 2016-03-04 02:14:23

Re: [SOLVED] VirtualBox modules don't load after upgrade to kernel 4.4.3-1

#19 2016-03-04 02:30:12

Re: [SOLVED] VirtualBox modules don't load after upgrade to kernel 4.4.3-1

#20 2016-03-04 02:38:55

Re: [SOLVED] VirtualBox modules don't load after upgrade to kernel 4.4.3-1

#21 2016-03-04 04:46:44

Re: [SOLVED] VirtualBox modules don't load after upgrade to kernel 4.4.3-1

#22 2016-03-04 05:27:47

Re: [SOLVED] VirtualBox modules don't load after upgrade to kernel 4.4.3-1

#23 2016-03-04 05:59:29

Re: [SOLVED] VirtualBox modules don't load after upgrade to kernel 4.4.3-1

#24 2016-03-04 08:43:10

Re: [SOLVED] VirtualBox modules don't load after upgrade to kernel 4.4.3-1

#25 2016-03-04 18:58:25

Re: [SOLVED] VirtualBox modules don't load after upgrade to kernel 4.4.3-1

Board footer