Official kernel.org 3.18.3 (custom config) : virtualbox-dkms 4.3.10-dfsg-1ubuntu1: virtualbox kernel module failed to build

Bug #1413947 reported by Yvon TANGUY
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
virtualbox (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Maybe for kernel >= 3.17, the file "vboxnetadp/linux/VBoxNetAdp-linux.c" need also one patch.
In the previous version of the VBox package I also patch the file "r0drv/linux/alloc-r0drv-linux.c"
See patchs attachments.

Note: I have done theses patch to make VBox working, I'm not an expert in the Linux kernel, nor VirtualBox code!
Since the kernel 3.7.0-rc3 was out, I ran VirtualBox with no problem.
Currently tested Linux kernel: 3.18.3.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: virtualbox-dkms 4.3.10-dfsg-1ubuntu1
Uname: Linux 3.18.3-1-custom x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
DKMSKernelVersion: 3.18.3-1-custom
Date: Fri Jan 23 11:36:38 2015
DuplicateSignature: dkms:virtualbox-dkms:4.3.10-dfsg-1ubuntu1:/var/lib/dkms/virtualbox/4.3.10/build/vboxnetadp/linux/VBoxNetAdp-linux.c:186:48: error: macro "alloc_netdev" requires 4 arguments, but only 3 given
InstallationDate: Installed on 2014-04-28 (269 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitecture: all
PackageVersion: 4.3.10-dfsg-1ubuntu1
SourcePackage: virtualbox
SystemImageInfo: Error: [Errno 2] Aucun fichier ou dossier de ce type: 'system-image-cli'
Title: virtualbox-dkms 4.3.10-dfsg-1ubuntu1: virtualbox kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)
VirtualBox.ModInfo:

Revision history for this message
Yvon TANGUY (vono22) wrote :
Revision history for this message
Yvon TANGUY (vono22) wrote :

Also, note that I didn't check upstream to see if it was fixed !

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

Hi, yes, they are both fixed upstream

https://www.virtualbox.org/changeset/52420/vbox/trunk/src/VBox/HostDrivers/VBoxNetAdp/linux/VBoxNetAdp-linux.c

https://www.virtualbox.org/changeset?reponame=vbox&old=52420%40trunk%2Fsrc%2FVBox%2FRuntime%2Fr0drv%2Flinux%2Falloc-r0drv-linux.c&new=52420%40trunk%2Fsrc%2FVBox%2FRuntime%2Fr0drv%2Flinux%2Falloc-r0drv-linux.c

Unfortunately I won't backport any patch to trusty until somebody push prior the new kernel on the repository...

Supporting such kind of unsupported configurations is so painful, specially for virtualbox.

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

You can see the whole changeset here
https://www.virtualbox.org/changeset/52420/vbox

Changed in virtualbox (Ubuntu):
status: New → Incomplete
Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

I subriscribe ubuntu-sponsors, if some sponsor have a different opinion I'll be glad to prepare the patch.

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

BTW the changeset has not (yet) been released in any stable virtualbox version.

Revision history for this message
Yvon TANGUY (vono22) wrote :

Not a problem, I was expecting this kind of answer ;-)

Revision history for this message
Yvon TANGUY (vono22) wrote :

I created the bug, only because apport popup. I didn't do it the first time.

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

yes, I understand, and your bug report will help users facing similar problems to solve them :)

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

Hi Yvon, can you please try with 4.3.20? just to be sure it isn't fixed in vivid too

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1358157, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

Revision history for this message
Erik M (erik-martens) wrote :

This error came up for me after updating on 14.04 from kernel 3.13 -> 3.16.

(I was aware of this error being reported previously, and I tried 3.18 the boot of which ended in kernel panic, so I decided to go for 3.16 to fix a HW related problem, which worked, as I do not need virtualbox currently)

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.