[SRU] Trouble installing mainline kernel 4.8: virtualbox-dkms 5.0.24-dfsg-0ubuntu1.16.04.1: virtualbox kernel module failed to build

Bug #1629870 reported by hasno
148
This bug affects 31 people
Affects Status Importance Assigned to Milestone
virtualbox (Ubuntu)
Fix Released
Critical
lohith n
Xenial
Fix Released
Critical
Unassigned
virtualbox-ext-pack (Ubuntu)
Fix Released
Undecided
Unassigned
Xenial
Fix Released
Undecided
Unassigned
virtualbox-guest-additions-iso (Ubuntu)
Fix Released
Undecided
Unassigned
Xenial
Fix Released
Undecided
Unassigned

Bug Description

[SRU Template ]
* the virtualbox kernel module needs some tweaks for the new kernel 4.8.
Using 5.0.24 and patching it is not quite easy, because we get less testing and diverge from upstream.
* We already did some minor release bump on xenial, without issues, and I think 5.0.30 is the best candidate to go in updates right now, fixing only bugs since 5.0.24 and keeping the kernel modules up-to-date.

ext-pack and guest-additions should follow the same way

(a 5.1 upload would be nice, but too many changes)

CHANGES since the last version:

 VirtualBox 5.0.32 (released 2017-01-17)

This is a maintenance release. The following items were fixed and/or added:

    GUI: fixed a problem where the new version detected dialog was covered by the appliance import dialog (Mac OS X hosts only; bug #16238)
    Storage: fixed a problem with the LsiLogic SCSI controller where requests could be lost with SMP guests
    OVF: when importing appliances, make sure that the version of the embedded VirtualBox specific settings is processed, to get the default settings handling right
    Linux hosts: automatically disable asynchronous I/O on Linux 2.6.18 kernels as high I/O load may trigger kernel oopses on these kernels if this feature is enabled
    API: don't crash when sanitizing certain VM names (bug #16299)
    Linux hosts / guests: Linux 2.6.28 compile fix (bug #16267)
    Linux hosts: compile Linux 4.9 compile fix (bug #16286)
    Linux hosts: Linux 4.10 fixes
    Linux Additions: fixed protocol error during certain operations on shared folders (bug #8463)

 VirtualBox 5.0.30 (released 2016-11-23)
    Storage: fixed resizing VDI images resulting in an unbootable image under certain circumstances (bug #15983)
    NAT: fixed several 5.0.28 regressions on Mac OS X and Windows hosts (bug #16084)
    Audio: fixed recording glitches (Mac OS X hosts)
    Audio: fixed stream re-initialization on audio device change (Mac OS X hosts)
    Windows hosts: hardening fix for Windows 10 build 14971 (bug #16202)
    Linux hosts / guests: Linux 4.8 and 4.9 fixes (bugs #16081, #16132 and #16116)
VirtualBox 5.0.28 (released 2016-10-18)
    NAT: Don't exceed the maximum number of "search" suffixes. Patch from bug #15948.
    NAT: fixed parsing of port-forwarding rules with a name which contains a slash (bug #16002)
    NAT Network: when the host has only loopback nameserver that cannot be mapped to the guests (e.g. dnsmasq running on 127.0.1.1), make DHCP supply NAT Network DNS proxy as nameserver.
    Bridged Network: prevent flooding syslog with packet allocation error messages (bug #15569)
    USB: fixed a possible crash when detaching a USB device
    Audio: fixes for recording (Mac OS X hosts only)
    Audio: now using Audio Queues on Mac OS X hosts
    OVF: improve importing of VMs created by VirtualBox 5.1
    VHDX: fixed cloning images with VBoxManage clonehd (bug #14288)
    Storage: Fixed broken bandwidth limitation when the limit is very low (bug #14982)
    Serial: Fixed high CPU usage with certain USB to serial converters on Linux hosts (bug #7796)
    BIOS: fixed 4bpp scanline calculation (bug #15787)
    VBoxManage: Don't try to set the medium type if there is no change (bug #13850)
    API: fixed initialization of SAS controllers (bug #15972)
    Linux hosts: don't use 32-bit legacy capabilities
    Linux hosts / guests: fix for kernels with CONFIG_CPUMASK_OFFSTACK set (bug #16020)
    Linux Additions: several fixes for X11 guests running non-root X servers
    Linux Additions: fix for Linux 4.7 (bug #15769)
    Linux Additions: fix for the display kmod driver with Linux 4.8 (bugs #15890 and #15896)
    Windows Additions: auto-resizing fixes for Windows 10 guests (bug #15257)
    Windows Additions: fixes for arranging the guest screens in multi-screen scenarios
    Windows Additions / VGA: if the guest's power management turns a virtual screen off, blank the corresponding VM window rather than hide the VM window
    Windows Additions: fixed a generic bug which could lead to freezing shared folders (bug #15662)

VirtualBox 5.0.26 (released 2016-07-18)
    VMM: fixed a bug in the task switching code (ticket #15571)
    GUI: allow to overwrite an existing file when saving a log file (bug #8034)
    GUI: fixed screenshot if the VM is started in separate mode
    Audio: improved recording from USB headsets and other sources which might need conversion of captured data
    Audio: fixed regression of not having any audio available on Solaris hosts
    VGA: fixed an occasional hang when running Windows guests with 3D enabled
    Storage: fixed a possible endless reconnect loop for the iSCSI backend if connecting to the target succeeds but further I/O requests cause a disconnect
    Storage: fixed a bug when resizing certain VDI images which resulted in using the whole disk on the host (bug #15582)
    EFI: fixed access to devices attached to SATA port 2 and higher (bug #15607)
    API: fixed video recording with VBoxHeadless (bug #15443)
    API: don't crash if there is no graphics controller configured (bug #15628)
    VBoxSVC: fixed several memory leaks when handling .dmg images
    Solaris hosts: fixed a crash on hosts with certain CPU configurations
    Windows hosts: properly fall back to NDIS5 on pre-Vista hosts on silent installations

[Impact]
Installed mainline kernel 4.8 on Ubuntu 16.04.1 x64 and got this error. Should I uninstall and return to 4.7.6?

[ Regression Potential ]
* it should be minimal, even if the debdiff looks scary, upstream has testsuites and a lot of people testing it.
Not diverging from upstream makes me more confident about the sanity of the upload.
(I would be more scared about cherry-picking individual patches because the kernel module might affect the interation with the virtulabox code, and it is not trivial to extract such patches)

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: virtualbox-dkms 5.0.24-dfsg-0ubuntu1.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
DKMSKernelVersion: 4.8.0-040800-generic
Date: Mon Oct 3 15:03:11 2016
DuplicateSignature: dkms:virtualbox-dkms:5.0.24-dfsg-0ubuntu1.16.04.1:/var/lib/dkms/virtualbox/5.0.24/build/vboxdrv/r0drv/linux/timer-r0drv-linux.c:364:13: error: implicit declaration of function ‘mod_timer_pinned’ [-Werror=implicit-function-declaration]
InstallationDate: Installed on 2016-05-14 (141 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
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: No upgrade log present (probably fresh install)

[ Test case ]
Installing virtualbox from proposed should work.

Revision history for this message
hasno (c1248408) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

Or use my ppa
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/virtualbox-ppa

or use virtualbox-source and build it yourself with module-assistant :)

Changed in virtualbox (Ubuntu):
status: New → Invalid
Revision history for this message
hasno (c1248408) wrote :

Why? I thought that updating the kernel independently of the rest of the system is the great benefit of linux and now that is not true? Because of virtualization being special? I don't understand.

Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

Virtualbox has a kernel module, that needs to be updated together with the kernel itself.
So, if you want, you can:
1) update virtualbox from my ppa
2) change the code to match the new kernel by using virtualbox-source
3) keep the old kernel.

virtualization *is* special :)

Revision history for this message
hasno (c1248408) wrote :

Thank you! So, will I have to install the 4.8 kernel again after updating virtualbox, or would the kernel already work and this is only required for virtualbox?

Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

the latter, but I still don't get why are you using the kernel ppa but not the virtualbox one
(considering I'm the vbox Ubuntu and Debian maintainer, BTW)

Revision history for this message
hasno (c1248408) wrote :

Oh dear, seems I made it more complicated then necessary :-)

I am not using the kernel ppa like a ppa at all. Instead I regularly check http://kernel.ubuntu.com/~kernel-ppa/mainline/ and if there is a new kernel, I manually remove the old kernel and manually install the new kernel. Newer realized that I could use it like a ppa (it does not contain the same information like launchpad where you get instructions how to integrate the ppa into your system) - the tutorials to get a more recent kernel did not mention that and it was working until now.

Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

the same happens to virtualbox, that is updated when kernel is updated.
go in the ppa page, and download the updated binary :)
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/virtualbox-ppa/+packages

Revision history for this message
hasno (c1248408) wrote :

Well, seems there is no easy way to integrate the mainline kernel ppa into the system, but at least I can use the virtualbox ppa. Btw: what is the difference between your ppa and the oracle repository?

Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

my ppa (the official Debian and Ubuntu package), has more subpackages, is built against system libraries, and handles the modules build in the dkms debian friendly way
(as well as a ton of other differences).

Revision history for this message
hasno (c1248408) wrote :

Sorry to bother you again, but is this expected:

DKMS: install completed.
Job for virtualbox.service failed because the control process exited with error code. See "systemctl status virtualbox.service" and "journalctl -xe" for details.
invoke-rc.d: initscript virtualbox, action "restart" failed.
virtualbox (5.1.6-dfsg-1~ubuntu16.04.1~ppa1) wird eingerichtet ...
vboxweb.service is a disabled or a static unit, not starting it.
Job for virtualbox.service failed because the control process exited with error code. See "systemctl status virtualbox.service" and "journalctl -xe" for details.
invoke-rc.d: initscript virtualbox, action "restart" failed.
virtualbox-qt (5.1.6-dfsg-1~ubuntu16.04.1~ppa1) wird eingerichtet ...
Trigger für shim-signed (1.18~16.04.1+0.8-0ubuntu2) werden verarbeitet ...

(I aborted the "deactivate secure boot" dialog because I thought that I have disabled secure boot in the past)

Since I have not removed the old virtualbox install, I went to the ubuntu software-center and uninstalled virtualbox, then used apt-get install virtualbox and I get:
"virtualbox already up to date (5.1.6-dfsg-1~ubuntu16.04.1~ppa1)"

So it seems the old virtualbox has not been overwritten with your version but kept in parallel? But the icon is gone and trying to start it from the terminal results in:
"The application virtualbox is currently not installed"

Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

sudo apt-get remove --purge virtualbox-5.1 virtualbox-5.0 or whatever should remove the old one correctly

Revision history for this message
hasno (c1248408) wrote :

Thanks!

Revision history for this message
Vasya Pupkin (shadowlmd) wrote :

Alternatively maintainer could update VirtualBox to something less ancient so it would work with newer kernels.

Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

5.0.24 has been released in june, 3 months ago.
Are you serious?

Revision history for this message
Stefan (tecoscr) wrote :

I tried to install from the PPA linked above (https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/virtualbox-ppa), but it made things worse. The installation didn't go through. Instead, there's an error message.

Setting up virtualbox-ext-pack (5.1.8-1~ubuntu16.04.1~ppa1) ...
virtualbox-ext-pack: downloading: http://download.virtualbox.org/virtualbox/5.1.8/Oracle_VM_VirtualBox_Extension_Pack-5.1.8.vbox-extpack
The file will be downloaded into /usr/share/virtualbox-ext-pack
/usr/lib/virtualbox/VBoxManage: error while loading shared libraries: VBoxDDU.so: cannot open shared object file: No such file or directory
dpkg: error processing package virtualbox-ext-pack (--configure):
 subprocess installed post-installation script returned error exit status 127
Errors were encountered while processing:
 virtualbox-ext-pack
E: Sub-process /usr/bin/dpkg returned an error code (1)

Now Synaptic lists the packages as installed, but they do not run. Removing them also won't work, yielding yet another error message:
E: virtualbox-ext-pack: subprocess installed pre-removal script returned error exit status 127

Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

please run

ls -l /usr/lib/virtualbox/VBoxDDU.so*

thanks

Revision history for this message
Michael Stucki (mstucki) wrote :

Check this thread which contains a patch that can be applied onto virtualbox-5.0.24 when using kernel 4.8: https://forums.gentoo.org/viewtopic-p-7974714.html

Revision history for this message
robepisc (robepisc) wrote :

I incurred in this same bug after installing the proposed HWE kernel (that AFAIK is expected to be released with the incoming 16.04.2 LTS point release) in my Xenial machine.

I installed the 4.8.0-32.34~16.04.1 kernel (from the proposed channel) today, after reading the request for testing that Leann Ogasawara posted one month ago to the Ubuntu Announce list.

However, after I executed "sudo apt-get install linux-generic-hwe-16.04-edge", Apport catched a DKMS problem that it recognized as a duplicate of this bug.

I think VirtualBox should work out-of-the-box with the HWE kernel.

Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

use my ppa for now

Revision history for this message
Kwang Moo Yi (kwang-m-yi) wrote :

I agree with robepisc on this that it should work out-of-the-box with the new kernel. Otherwise, this package would become useless. This bug honestly should be a blocker for the point release.

Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

how can I install the new kernel on xenial?

Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

Hello, I updated the virtualbox* stuff in ppa:costamagnagianfranco/locutusofborg-ppa

 virtualbox-guest-additions-iso - 5.0.30-0ubuntu1.16.04.2
 virtualbox-ext-pack - 5.0.30-0ubuntu1.16.04.2
 virtualbox - 5.0.30-dfsg-0ubuntu1.16.04.2

can you please help me in testing them? after the test is successful I'll upload in xenial -proposed pocket and ask an SRU

Changed in virtualbox (Ubuntu):
status: Invalid → New
importance: Undecided → Critical
status: New → Fix Released
Changed in virtualbox (Ubuntu Xenial):
importance: Undecided → Critical
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in virtualbox (Ubuntu Xenial):
status: New → Confirmed
Revision history for this message
Vaclav Rehak (vaclav-n) wrote :

To install the new kernel on xenial, enable Pre-release updates (xenial-proposed) in System Settings - Software & Updates - Developer Options and run
sudo apt-get install linux-generic-hwe-16.04-edge

After reboot you'll probably get this error.

Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

I uploaded 5.0.30 in my ppa and in xenial- queue

summary: - Trouble installing mainline kernel 4.8: virtualbox-dkms
+ [SRU] Trouble installing mainline kernel 4.8: virtualbox-dkms
5.0.24-dfsg-0ubuntu1.16.04.1: virtualbox kernel module failed to build
description: updated
Changed in virtualbox (Ubuntu Xenial):
status: Confirmed → Fix Committed
Revision history for this message
Kwang Moo Yi (kwang-m-yi) wrote :

I can confirm that 5.0.30 in your ppa works :-)

Revision history for this message
Łukasz Zemczak (sil2100) wrote :

This seems to be a rather big change so I would appreciate if the bug could also include the Regression Potential field from the SRU template in the bug description. Would be also good if you could include a list of changes coming with this release in comparison to the previous version so that we know if it's indeed only fixing bugs (as you have done it in the previous virtualbox SRU bug).

Thanks!

Changed in virtualbox-ext-pack (Ubuntu):
status: New → Fix Released
Changed in virtualbox-guest-additions-iso (Ubuntu):
status: New → Fix Released
Changed in virtualbox-ext-pack (Ubuntu Xenial):
status: New → Fix Committed
Changed in virtualbox-guest-additions-iso (Ubuntu Xenial):
status: New → Fix Committed
Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

I did it :) for guest-additions and ext-pack only a subset of the changelog applies, but they are part of the same codebase (IIRC), and they should (IMAO) be handled together

description: updated
Revision history for this message
lohith n (lohithn4) wrote :

Been getting this bug

Changed in virtualbox (Ubuntu):
assignee: nobody → lohith n (lohithn4)
description: updated
Revision history for this message
Kwang Moo Yi (kwang-m-yi) wrote :

As in the comments, indeed 5.1 changes too much. It actually has regression problems with i3wm (which was fixed in one of the versions, but now back...)

Also 5.0.32 is at the ppa but not in xenial-proposed. :-)

Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

it is in unapproved queue, waiting for an Ubuntu-Release team member
https://launchpad.net/ubuntu/xenial/+queue?queue_state=1&queue_text=

Revision history for this message
Chris J Arges (arges) wrote : Please test proposed package

Hello hasno, or anyone else affected,

Accepted virtualbox into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/virtualbox/5.0.32-dfsg-0ubuntu1.16.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

tags: added: verification-needed
Revision history for this message
Chris J Arges (arges) wrote :

Hello hasno, or anyone else affected,

Accepted virtualbox-guest-additions-iso into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/virtualbox-guest-additions-iso/5.0.32-0ubuntu1.16.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Revision history for this message
Chris J Arges (arges) wrote :

Hello hasno, or anyone else affected,

Accepted virtualbox-ext-pack into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/virtualbox-ext-pack/5.0.32-0ubuntu1.16.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

testing when dinstall finishes

Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

confirmed the fix from xenial-proposed on my testing VM

tags: added: verification-done
removed: verification-needed
Revision history for this message
Kwang Moo Yi (kwang-m-yi) wrote :

I tested the package on my 16.04.1 with linux-hwe-16.04-edge and confirmed that it works :-)

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package virtualbox - 5.0.32-dfsg-0ubuntu1.16.04.2

---------------
virtualbox (5.0.32-dfsg-0ubuntu1.16.04.2) xenial; urgency=medium

  * New upstream release, fixing new kernel build issues (LP: #1629870)

 -- Gianfranco Costamagna <email address hidden> Wed, 11 Jan 2017 09:38:42 +0100

Changed in virtualbox (Ubuntu Xenial):
status: Fix Committed → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote : Update Released

The verification of the Stable Release Update for virtualbox has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package virtualbox-guest-additions-iso - 5.0.32-0ubuntu1.16.04.2

---------------
virtualbox-guest-additions-iso (5.0.32-0ubuntu1.16.04.2) xenial; urgency=medium

  * Update to the latest minor release for xenial (LP: #1629870)

 -- Gianfranco Costamagna <email address hidden> Wed, 11 Jan 2017 12:43:32 +0100

Changed in virtualbox-guest-additions-iso (Ubuntu Xenial):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package virtualbox-ext-pack - 5.0.32-0ubuntu1.16.04.2

---------------
virtualbox-ext-pack (5.0.32-0ubuntu1.16.04.2) xenial; urgency=medium

  * Update to the latest minor release for xenial (LP: #1629870)

 -- Gianfranco Costamagna <email address hidden> Wed, 11 Jan 2017 12:39:14 +0100

Changed in virtualbox-ext-pack (Ubuntu Xenial):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.