virtualbox-dkms 5.0.24-dfsg-0ubuntu1.16.04.1: virtualbox kernel module failed to build

[Dave Odell]

Difficulty: 64-bit kernel w/ 32-bit userspace during a 14.04 LTS -> 16.04 LTS system upgrade.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: virtualbox-dkms 5.0.24-dfsg-0ubuntu1.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
DKMSKernelVersion: 4.4.0-31-generic
Date: Mon Aug 1 17:33:52 2016
PackageArchitecture: all
PackageVersion: 5.0.24-dfsg-0ubuntu1.16.04.1
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt 1.2.12~ubuntu16.04.1
SourcePackage: virtualbox
Title: virtualbox-dkms 5.0.24-dfsg-0ubuntu1.16.04.1: virtualbox kernel module failed to build
UpgradeStatus: Upgraded to xenial on 2016-08-01 (0 days ago)

[Gianfranco Costamagna (costamagnagianfranco)]

hi, can you please remove it and reinstall it again? do you have some particular configuration on your pc?

[Sergiu (serrvius)]

Hi, thancks for suggestion, no i use the default configuration i try now reinstall it and try to open again, but this error is appear at start computer but Virtual box work ok

[Dave Odell (dmo2118)]

Well, now that the upgrade is complete, GRUB lets me boot, and all my packages are up-to-date, I get no DKMS build errors when I uninstall and reinstall virtualbox/virtualbox-qt/virtualbox-dkms.

Instead, when I try to start a VM:

RTR3InitEx failed with rc=-1912 (rc=-1912)

The VirtualBox kernel modules do not match this version of VirtualBox. The installation of VirtualBox was apparently not successful. Executing

'modprobe vboxdrv'

may correct this. Make sure that you do not mix the OSE version and the PUEL version of VirtualBox.

where: supR3HardenedMainInitRuntime what: 4 VERR_VM_DRIVER_VERSION_MISMATCH (-1912) - The installed support driver doesn't match the version of the user.

...But that's unrelated to the original bug report.

I'll probably just go back to a 32-bit kernel at some point. That will probably be sufficient to get VirtualBox working again once I need it.

(Odd: I got an e-mail when Sergiu posted, but not when LocutusOfBorg posted.)

[Gianfranco Costamagna (costamagnagianfranco)]

can you please run:
find /lib/modules/ -name "*vbox*.ko*" -exec modinfo "{}" \;

thanks

[Dave Odell (dmo2118)]

There were some old VirtualBox kernel modules lying around in /lib/modules from old Linux 3.x kernels. I cleaned those out and rebooted; no change though.

Incidentally: $ uname -a
Linux dhcppc6 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

I'm suspecting that the VERR_VM_DRIVER_VERSION_MISMATCH is caused by a mismatched kernel/userspace CPU architecture.

filename: /lib/modules/4.4.0-34-generic/kernel/ubuntu/vbox/vboxsf/vboxsf.ko
version: 5.0.18_Ubuntu (interface 0x00010004)
license: GPL
author: Oracle Corporation
description: Oracle VM VirtualBox VFS Module for Host File System Access
srcversion: BC8A42B58B023C5DA0FB887
depends: vboxguest
intree: Y
vermagic: 4.4.0-34-generic SMP mod_unload modversions
parm: follow_symlinks:Let host resolve symlinks rather than showing them (int)
filename: /lib/modules/4.4.0-34-generic/kernel/ubuntu/vbox/vboxvideo/vboxvideo.ko
version: 5.0.18_Ubuntu
license: GPL and additional rights
description: Oracle VM VirtualBox Graphics Card
author: Oracle Corporation
srcversion: 13C89163828486B6D203AF8
alias: pci:v000080EEd0000BEEFsv*sd*bc*sc*i*
depends: drm,drm_kms_helper,ttm,vboxguest,syscopyarea,sysfillrect,sysimgblt
intree: Y
vermagic: 4.4.0-34-generic SMP mod_unload modversions
parm: modeset:Disable/Enable modesetting (int)
filename: /lib/modules/4.4.0-34-generic/kernel/ubuntu/vbox/vboxguest/vboxguest.ko
version: 5.0.18_Ubuntu
license: GPL
description: Oracle VM VirtualBox Guest Additions for Linux Module
author: Oracle Corporation
srcversion: A2B0E3228AD033CF730FD74
alias: pci:v000080EEd0000CAFEsv00000000sd00000000bc*sc*i*
depends:
intree: Y
vermagic: 4.4.0-34-generic SMP mod_unload modversions
filename: /lib/modules/4.4.0-34-generic/updates/dkms/vboxnetadp.ko
version: 5.0.24_Ubuntu r108355 ((0xA2CDe001U))
license: GPL
description: Oracle VM VirtualBox Network Adapter Driver
author: Oracle Corporation
srcversion: 3B529F79361618821A0E936
depends: vboxdrv
vermagic: 4.4.0-34-generic SMP mod_unload modversions
filename: /lib/modules/4.4.0-34-generic/updates/dkms/vboxdrv.ko
version: 5.0.24_Ubuntu r108355 (0x00240000)
license: GPL
description: Oracle VM VirtualBox Support Driver
author: Oracle Corporation
srcversion: 8BDFE76560DDFC614398609
depends:
vermagic: 4.4.0-34-generic SMP mod_unload modversions
parm: force_async_tsc:force the asynchronous TSC mode (int)
filename: /lib/modules/4.4.0-34-generic/updates/dkms/vboxnetflt.ko
version: 5.0.24_Ubuntu r108355 ((0xA2CDe001U))
license: GPL
description: Oracle VM VirtualBox Network Filter Driver
author: Oracle Corporation
srcversion: 61D17D9C70C97A37C4DF23B
depends: vboxdrv
vermagic: 4.4.0-34-generic SMP mod_unload modversions
filename: /lib/modules/4.4.0-34-generic/updates/dkms/vboxpci.ko
version: 5.0.24_Ubuntu r108355
license: GPL
description: ...

[Gianfranco Costamagna (costamagnagianfranco)]

I'm not sure how can you run an amd64 kernel with an i386 system, but in this case I might suggest you to use virtualbox-source package, and manually build the modules with module-assistant tool.
I don't think your configurationis supported unfortunately.

[Dave Odell (dmo2118)]

It's a MultiArch installation: <https://help.ubuntu.com/community/MultiArch>. 64-bit CPU (currently), 64-bit kernel (i.e. linux-image-generic:amd64), 32-bit userspace with a handful of 64-bit packages mixed in. It works (except for VirtualBox).

Also, I tried module-assistant with virtualbox-source, and in the process of installing virtualbox-modules-4.4.0-34-generic, I get...

(snip)
The following packages will be REMOVED:
  grub-efi-amd64 grub-efi-amd64-signed:amd64
  virtualbox-modules-4.4.0-34-generic
(snip)
Do you want to continue? [Y/n] Holy crap, no.

(This is fun!)

Again though, I'll just switch to a 32-bit kernel when I need VirtualBox on here.

[Gianfranco Costamagna (costamagnagianfranco)]

>It's a MultiArch installation: <https://help.ubuntu.com/community/MultiArch>. 64-bit CPU >(currently), 64-bit kernel (i.e. linux-image-generic:amd64), 32-bit userspace with a handful of >64-bit packages mixed in. It works (except for VirtualBox).

multiarch is perfectly supported by virtualbox

>Also, I tried module-assistant with virtualbox-source, and in the process of installing virtualbox->modules-4.4.0-34-generic, I get...

> grub-efi-amd64 grub-efi-amd64-signed:amd64
> virtualbox-modules-4.4.0-34-generic

yes, because you need to build a deb package if you compile it from source.
Can you please try my ppa?
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/virtualbox-ppa

[Launchpad Janitor (janitor)]

[Expired for virtualbox (Ubuntu) because there has been no activity for 60 days.]

[Dave Odell (dmo2118)]

(I'm back. Sorry about the delay, kind of lost track of everything. I'm still not getting e-mails despite seeing "You are subscribed to all notifications for this bug." at the top of this page. I'll try to keep F5'ing this thread for the next two/three weeks or so.)

Added your PPA, aptitude(8) now shows VirtualBox packages 5.1.8.

No love with virtualbox-dkms; I still get the same business with rc=-1912.

With virtualbox-source, it still wants to remove grub-efi-amd64 and grub-efi-amd64-signed. Not cool!

Trying to install virtualbox:amd64 instead of the 32-bit version, apt-get(8) gives me:
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 virtualbox:amd64 : Depends: virtualbox-dkms:amd64 (>= 5.1.8-dfsg-6~ubuntu16.04.1~ppa1) but it is not installable or
                             virtualbox-source:amd64 (>= 5.1.8-dfsg-6~ubuntu16.04.1~ppa1) but it is not installable or
                             virtualbox-modules:amd64 but it is not installable
                    Depends: python3:amd64 (< 3.6) but it is not going to be installed
                    Depends: python3:amd64 (>= 3.5~) but it is not going to be installed
                    Depends: python3.5:amd64 but it is not going to be installed

Let me know if there's anything else you want me to try.

[Gianfranco Costamagna (costamagnagianfranco)]

Can you please try 5.1.10? I just uploaded it to my ppa

[Gianfranco Costamagna (costamagnagianfranco)]

also, don't try virtualbox-source, remove it and use virtualbox-dkms, since this one should support kernels up to 4.9

[Dave Odell (dmo2118)]

GUI reports 5.1.10_Ubuntu r112026. virtualbox-dkms is at 5.1.10-dfsg-1~ubuntu16.04.1~ppa1. virtualbox-source is gone. Still get -1912.

[Gianfranco Costamagna (costamagnagianfranco)]

please try ppa:costamagnagianfranco/costamagnagianfranco-ppa, I did some changes.
And please report exactly what you get after
modprobe vboxdrv

thanks

[Dave Odell (dmo2118)]

(You mean ppa:costamagnagianfranco/virtualbox-ppa, not ppa:costamagnagianfranco/costamagnagianfranco-ppa, right? I'm not seeing VirtualBox in the second one.)

Upgraded virtualbox/virtualbox-qt/virtualbox-dkms (5.1.10-dfsg-2~ubuntu16.04.1~ppa1), rebooted, no luck, still get rc=-1912.

modprobe(8) does not give me much:

user@dhcppc6:~$ sudo modprobe vboxdrv
[sudo] password for user:
user@dhcppc6:~$ sudo modprobe -vvv vboxdrv
modprobe: INFO: ../libkmod/libkmod.c:364 kmod_set_log_fn() custom logging function 0x565d9230 registered
modprobe: DEBUG: ../libkmod/libkmod-index.c:755 index_mm_open() file=/lib/modules/4.4.0-47-generic/modules.dep.bin
modprobe: DEBUG: ../libkmod/libkmod-index.c:755 index_mm_open() file=/lib/modules/4.4.0-47-generic/modules.alias.bin
modprobe: DEBUG: ../libkmod/libkmod-index.c:755 index_mm_open() file=/lib/modules/4.4.0-47-generic/modules.symbols.bin
modprobe: DEBUG: ../libkmod/libkmod-index.c:755 index_mm_open() file=/lib/modules/4.4.0-47-generic/modules.builtin.bin
modprobe: DEBUG: ../libkmod/libkmod-module.c:556 kmod_module_new_from_lookup() input alias=vboxdrv, normalized=vboxdrv
modprobe: DEBUG: ../libkmod/libkmod-module.c:562 kmod_module_new_from_lookup() lookup modules.dep vboxdrv
modprobe: DEBUG: ../libkmod/libkmod.c:574 kmod_search_moddep() use mmaped index 'modules.dep' modname=vboxdrv
modprobe: DEBUG: ../libkmod/libkmod.c:402 kmod_pool_get_module() get module name='vboxdrv' found=(nil)
modprobe: DEBUG: ../libkmod/libkmod.c:410 kmod_pool_add_module() add 0x57561168 key='vboxdrv'
modprobe: DEBUG: ../libkmod/libkmod-module.c:202 kmod_module_parse_depline() 0 dependencies for vboxdrv
modprobe: DEBUG: ../libkmod/libkmod-module.c:583 kmod_module_new_from_lookup() lookup vboxdrv=0, list=0x57561238
modprobe: DEBUG: ../libkmod/libkmod.c:501 lookup_builtin_file() use mmaped index 'modules.builtin' modname=vboxdrv
modprobe: DEBUG: ../libkmod/libkmod-module.c:468 kmod_module_unref() kmod_module 0x57561168 released
modprobe: DEBUG: ../libkmod/libkmod.c:418 kmod_pool_del_module() del 0x57561168 key='vboxdrv'
modprobe: INFO: ../libkmod/libkmod.c:331 kmod_unref() context 0x57560118 released
user@dhcppc6:~$

Checking dmesg(1) shows nothing new when I do modprobe, but when I scroll up to system boot time, I do see:

[ 39.458177] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
[ 39.463587] vboxdrv: Found 2 processor cores
[ 39.465883] vboxdrv: fAsync=0 offMin=0x1b8 offMax=0x6fe
[ 39.566017] vboxdrv: TSC mode is Synchronous, tentative frequency 2660054213 Hz
[ 39.566019] vboxdrv: Successfully loaded version 5.1.10_Ubuntu (interface 0x00280000)
[ 39.612407] VBoxNetFlt: Successfully started.
[ 39.652449] VBoxNetAdp: Successfully started.
[ 39.687833] VBoxPciLinuxInit
[ 39.719866] vboxpci: IOMMU not found (not registered)

Apparently vboxdrv is being successfully loaded by the kernel.

[Gianfranco Costamagna (costamagnagianfranco)]

and virtualbox starts?
(my bad, I deleted virtualbox from costamagnagianfranco-ppa some hours ago, I moved the new build to virtualbox-ppa only)

[Dave Odell (dmo2118)]

Only the GUI starts. Like I said, trying to start a virtual machine gives me that rc=-1912 error.

[Gianfranco Costamagna (costamagnagianfranco)]

please run
ls /dev/vbox* -lh

thanks

[Gianfranco Costamagna (costamagnagianfranco)]

oh... did you upgrade your extpack package too?

[Dave Odell (dmo2118)]

$ ls /dev/vbox* -lh
crw------- 1 root root 10, 55 Dec 4 22:11 /dev/vboxdrv
crw------- 1 root root 10, 54 Dec 4 22:11 /dev/vboxdrvu
crw------- 1 root root 10, 53 Dec 4 22:11 /dev/vboxnetctl

/dev/vboxusb:
total 0
drwxr-x--- 2 root vboxusers 80 Dec 4 22:12 002
drwxr-x--- 2 root vboxusers 60 Dec 4 22:11 005

I don't have the Oracle VM VirtualBox Extension Pack installed. I do show an active VNC extension package at version 5.1.10r112026.

Also, I was apparently not a member of the 'vboxusers' group. Adding myself to that group did not help, unfortunately.

On a related note: have a core dump. Apport has been -- intermittently -- nagging me about VirtualBox throwing SIGABRTs, apparently after I get the rc=-1912 error. I forget if it was doing that with 5.0.x.

[Gianfranco Costamagna (costamagnagianfranco)]

crw-rw-rw- 1 root root 10, 54 nov 30 10:14 /dev/vboxdrvu

please try sudo chmod 666 /dev/vboxdrvu

[Dave Odell (dmo2118)]

Nope, same thing. Sorry.

I also tried sudo chmod 666 `find /dev/vbox* -type c`. That didn't work either.

[Gianfranco Costamagna (costamagnagianfranco)]

How can you use 5.1.10r112026 with virtualbox 5.0.24?
I don't know what that active VNC extension is.

[Gianfranco Costamagna (costamagnagianfranco)]

http://download.virtualbox.org/virtualbox/5.1.10/UserManual.pdf
It is possible to install both the Oracle VM VirtualBox Extension Pack and VNC, but only one
VRDE module can be active at any time. The following command switches to the VNC VRDE
module in VNC:
VBoxManage setproperty vrdeextpack VNC
(don't know what does it mean)

[Dave Odell (dmo2118)]

I'm still using VirtualBox 5.1.10 from your PPA.

VNC is short for "Virtual Network Computing". It's for desktop sharing; with VirtualBox, you can use a VNC client (i.e. Vinagre, a.k.a Remote Desktop Viewer -- https://wiki.gnome.org/Apps/Vinagre) to access virtual machines over the network: view their display, and control their mouse and keyboard.

The Oracle VM VirtualBox Extension Pack comes with support for RDP ("Remote Desktop Protocol"), also for desktop sharing.

VirtualBox can have both extension packs installed, but only one can be providing remote display support at a time, which is what that vrdeextpack property is for.

Incidentally, removing the VNC extension doesn't fix rc=-1912.

[Gianfranco Costamagna (costamagnagianfranco)]

I'm out of ideas then :/

[Dave Odell (dmo2118)]

Don't worry about it, it's not that big of a deal on my end.

Thanks for trying, anyway.

[Dave Odell (dmo2118)]

Circumstances have compelled me to switch back to a 32-bit GRUB and Linux kernel. For what it's worth, VirtualBox is able to launch virtual machines now.

[Rolf Leggewie (r0lf)]

upstream confirms that running amd64 kernel with i386 virtualbox binary package is unsupported.

Marking as dupe to bug 1665424.