virtualbox-dkms 4.1.12-dfsg-2ubuntu0.6: virtualbox kernel module failed to build [error: incompatible types when returning type ‘kuid_t’ but ‘RTUID’ was expected]

[Jason M]

The virtualbox module does not build with the newer HWE kernels found in Ubuntu Precise/12.04

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.5
ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
Uname: Linux 3.13.0-14-generic i686
ApportVersion: 2.13.3-0ubuntu1
Architecture: i386
DKMSKernelVersion: 3.13.0-17-generic
Date: Thu Mar 13 12:40:09 2014
DuplicateSignature: dkms:virtualbox-dkms:4.1.12-dfsg-2ubuntu0.5:/var/lib/dkms/virtualbox/4.1.12/build/vboxdrv/linux/SUPDrv-linux.c:226:5: error: incompatible types when returning type ‘kuid_t’ but ‘RTUID’ was expected
InstallationDate: Installed on 2012-04-29 (682 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
PackageArchitecture: all
PackageVersion: 4.1.12-dfsg-2ubuntu0.5
SourcePackage: virtualbox
Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.5: virtualbox kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)
VirtualBox.ModInfo:

[Launchpad Janitor (janitor)]

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

[Legimet (legimet)]

Confirmed using saucy LTS enablement stack.

[Star Man (starman-deactivatedaccount)]

Upgraded Precise kernel and video stack to Trusty HWE, and then VirtualBox couldn't run. 'kernel module failed to build'

[steve jepson (stevejjepson)]

Is there any update on when this'll be tackled ?

FYI Opening a VirtualBox VM gives ;

Virtual Box - Error in suplibOsinit

The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing

'/etc/init.d/vboxdrv setup'

as root. If it is available in your distribution, you should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.

[soulsacrifire (simone-2)]

I've removed the virtualbox-dkms package and I was able to install the update. Then I've installed the virtualbox-dkms again with the erro No suitable module for running kernel .

[[e-mail] (nywest1)]

On 07/18/2014 04:20 AM, steve jepson wrote:
> Is there any update on when this'll be tackled ?
>
>
> FYI Opening a VirtualBox VM gives ;
>
> Virtual Box - Error in suplibOsinit
>
> The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or
> there is a permission problem with /dev/vboxdrv. Please reinstall the
> kernel module by executing
>
> '/etc/init.d/vboxdrv setup'
>
> as root. If it is available in your distribution, you should install the
> DKMS package first. This package keeps track of Linux kernel changes and
> recompiles the vboxdrv kernel module if necessary.
>
> thiss bug was related to another that was submitted and i'm guessing
> the problem will
      be fixed on that report and not this one.

** This bug has been marked a duplicate of bug 1292118

[soulsacrifire (simone-2)]

Hi Nywest,

thanks a lot for your information.
I'll check the 1292118 bug.

Regards.

[Daniel Letzeisen (dtl131)]

As I wrote in a duplicate bug:

Ubuntu will probably not put a new version of virtualbox in the main repo (because I don't think they guarantee upgrades of binary modules on LTS releases).

PPA is probably the best solution here: https://launchpad.net/~ricotz/+archive/ubuntu/virtualization

[Jørn (jbm131)]

Tried different solutions in forums without any luck.

I solved it by removing Virtualbox via softwarecenter and then using autoremove.

Then I downloaded and installed a new Virtualbox directly from Oracle after installing dkms.

Then everything worked again,- and my VM's was in place,- Virtualbox must do a backup somewhere which wasen't removed??

I was lucky :)

[Daniel Letzeisen (dtl131)]

Removing the old 4.1.x virtualbox package will not remove your virtual images or your user's configuration.

[Jørn (jbm131)]

Hi Daniel

I did not know that, but it saved me many hours of work :)

[Nicko Sinclair (nickosdrumpad)]

Yep, after removing 'virtualbox-dkms' and installing the new version (from Oracle) means I can run my VMs again.

[Robert D. Bowers (n4fbz)]

I finally got my VMs working... someone in Oracle needs to know that the PPA information they have is wrong (an error in one of the files Ubuntu looks to for setup information).

You need to physically download and install the latest version (after doing a basic removal of the old version - don't do a complete removal). Trying to keep the software updated by PPA won't work until the error on their end is fixed (as I remember, a missing source.list in the setup file).

[Clive Kirsten (ckirsten)]

wow, thanks to all, I am really surprised about so much solutions. Anyway, have choosen this and now it works again:

You need to physically download and install the latest version (after doing a basic removal of the old version - don't do a complete removal). Trying to keep the software updated by PPA won't work until the error on their end is fixed (as I remember, a missing source.list in the setup file).

Thanks Clive

[Daniel Letzeisen (dtl131)]

While one can work around this bug easily with third-party PPA's/packages, it is not considered Fix Released until an updated version of virtualbox is in the repo.

[Jørn (jbm131)]

Hi again

Something came up.

I did fix it as described above,- but:

I use wireless network to my Ubuntu,- and bridged network setup in the virtualbox options for the VM hosts.

When I ping something from the terminal, now I get duplicate answers?

Very strange, and it must be in connection with the repair described as above.

I will look further into it tomorrow.

B.R.
Jørn

[Jørn (jbm131)]

Really strange?

No change in setup at all. I get duplicate answers on wifi but it's ok on cable ethernet.
Only for VM machines in virtualbox,- not for the host Ubuntu.

This has something to do with the new kernel ... I have no idea?

[undefined (undefined)]

= SUMMARY =
this patch addresses the overarching virtualbox host linux kernel module source code and not the specific problem of integrating it into the dkms package/setup (which is left as an exercise to the reader). i demonstrate how to use the below patch with the virtual-source package (which is how i compile the virtualbox linux kernel modules).

= HOW-TO =
 * cd /usr/src
 * apt-get install virtualbox-source linux-headers-generic-lts-trusty module-assistant multitee
 * tar -xf virtualbox.tar.bz2
 * patch -p1 <virtualbox-source-vs-linux-headers-generic-lts-trusty.patch
 * m-a -t --not-unpack -k /usr/src/linux/ build virtualbox 2>&1 | multitee 0-1,2 2>virtualbox.log
 * dpkg -i virtualbox-modules-3.13.0-34-generic_4.1.12-dfsg-2ubuntu0.6+3.13.0-34.60~precise1_amd64.deb

= REFERENCES =
 * https://www.virtualbox.org/ticket/11664
  * https://www.virtualbox.org/changeset/45300/vbox

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "virtualbox-source-vs-linux-headers-generic-lts-trusty.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

[Stephen Baynes (stephen-baynes)]

Updated the hardware support stack in 12.04 as requested by update manager.
Rebooted. Tried to start virtualbox.
This failed Kernel driver not installed (rc=-1908)
Followed the instruction to do
/etc/init.d/vboxdrv setup
which failed as file does not exist.
So following various posts to resolve that did
apt-get remove virtualbox-dkms
apt-get purge virtualbox-dkms
apt-get install virtualbox-dkms
which failed as above.

[Vinícius Alves Hax (viniciushax)]

This bug also affects me. I follow the procedure suggested by jbm131.

This is the download link: https://www.virtualbox.org/wiki/Linux_Downloads

[Matthew Duffy (scratchtrax-o)]

After updating to the latest Ubuntu OS, this is np longer an issue foe
me and vBox works as it should

Sent from my Windows Phone From: Vinícius Alves Hax
Sent: ‎10/‎6/‎2014 1:11 PM
To: <email address hidden>
Subject: [Bug 1292118] Re: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.6:
virtualbox kernel module failed to build [error: incompatible types
when returning type ‘kuid_t’ but ‘RTUID’ was expected]
This bug also affects me. I follow the procedure suggested by jbm131.

This is the download link:
https://www.virtualbox.org/wiki/Linux_Downloads

--
You received this bug notification because you are subscribed to a
duplicate bug report (1357787).
https://bugs.launchpad.net/bugs/1292118

Title:
  virtualbox-dkms 4.1.12-dfsg-2ubuntu0.6: virtualbox kernel module
  failed to build [error: incompatible types when returning type
  ‘kuid_t’ but ‘RTUID’ was expected]

Status in “linux” package in Ubuntu:
  Triaged
Status in “virtualbox” package in Ubuntu:
  In Progress

Bug description:
  The virtualbox module does not build with the newer HWE kernels found
  in Ubuntu Precise/12.04

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.5
  ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
  Uname: Linux 3.13.0-14-generic i686
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: i386
  DKMSKernelVersion: 3.13.0-17-generic
  Date: Thu Mar 13 12:40:09 2014
  DuplicateSignature:
dkms:virtualbox-dkms:4.1.12-dfsg-2ubuntu0.5:/var/lib/dkms/virtualbox/4.1.12/build/vboxdrv/linux/SUPDrv-linux.c:226:5:
error: incompatible types when returning type ‘kuid_t’ but ‘RTUID’ was
expected
  InstallationDate: Installed on 2012-04-29 (682 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release
i386 (20120423)
  PackageArchitecture: all
  PackageVersion: 4.1.12-dfsg-2ubuntu0.5
  SourcePackage: virtualbox
  Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.5: virtualbox kernel
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  VirtualBox.ModInfo:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1292118/+subscriptions

[Daniel van Vugt (vanvugt)]

"In Progress" for two months without any progress. Unassigning...

[jaybo (ubuntu-one-ostaffe)]

Added HWE today, Ubuntu would not reboot.
Restored previous build, removed Virtual Box using Ubuntu Software Center
Re-installed HWE. Installation successful.
Re-installed Virtual Box using Ubuntu Software Center
Installation failed (re-building kernel?)
Removed Virtual Box using Ubuntu Software Center
Installed Virtual Box using instructions at https://www.virtualbox.org/wiki/Linux_Downloads
All is good now.

So why does Ubuntu Software Center still push a bad installation of Virtual Box? Shouldn't the version in Software Center be removed?

[Gianfranco Costamagna (costamagnagianfranco)]

fixed in utopic+

[Bill Ataras (signalman)]

I hope I haven't been sending a lot of duplicates. All I see is a
window that pops up announcing a "problem" and asking if I want to
report it. There isn't enough info for me to determine whether the
problem is a repeat of an earlier report, or something new.

Bill

On 12/11/2014 03:43 AM, LocutusOfBorg wrote:
> fixed in utopic+
>

--
Bill Ataras

[Gianfranco Costamagna (costamagnagianfranco)]

No Bill, it is everything ok :)

I'll ping some ubuntu folks on monday to get the fix landed :D

[undefined (undefined)]

better late than never; didn't realize i would have to do everything myself.

apt-get source virtualbox
cd virtualbox-4.1.12-dfsg
patch -p1 <../linux-3.13-virtualbox-host-kernel-modules.patch
apt-get install build-dep virtualbox
apt-get install devscripts fakeroot
debuild -i -us -uc
cd ..
dpkg -i virtualbox-dkms_4.1.12-dfsg-2ubuntu0.7_all.deb

[Gianfranco Costamagna (costamagnagianfranco)]

Please test "undefined"'s patch I uploaded into my ppa and report back.

thanks
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa

[Bill Ataras (signalman)]

When I executed the first line of your sequence below, I didn't get the
virtualbox version your second line needs. Instead, I got:
     virtualbox-4.3_4.3.16-95972~Ubuntu~raring_amd64.deb
It was dated Oct. 6, and located in ~/Downloads
Did I miss something?

Bill

On 12/15/2014 12:46 AM, undefined wrote:
> better late than never; didn't realize i would have to do everything
> myself.
>
> apt-get source virtualbox
> cd virtualbox-4.1.12-dfsg
> patch -p1 <../linux-3.13-virtualbox-host-kernel-modules.patch
> apt-get install build-dep virtualbox
> apt-get install devscripts fakeroot
> debuild -i -us -uc
> cd ..
> dpkg -i virtualbox-dkms_4.1.12-dfsg-2ubuntu0.7_all.deb
>
> ** Patch added: "patch to debian package to update host kernel module source code to 3.13"
> https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1292118/+attachment/4281280/+files/linux-3.13-virtualbox-host-kernel-modules.patch
>

--
Bill Ataras

[undefined (undefined)]

yes, that's because you don't have a pristine precise sources.list (ie no more than main, universe, multiverse, & restricted from precise, precise-updates, and precise-security; no ppas or backports).

apt-get source virtualbox=4.1.12-dfsg-2ubuntu0.6
apt-get build-dep virtualbox=4.1.12-dfsg-2ubuntu0.6

i did make a mistake earlier in saying "apt-get install build-dep", but a quick trip to the apt-get man page would have straightened a person out.

[Gianfranco Costamagna (costamagnagianfranco)]

Hi Bill, the patch was useful to me, to upload a fixed version into my ppa.
Now if you can test the ppa and report back positive feedbacks I'll ask a sponsor to make the fix be uploaded into the ubuntu repositories.

there is no more need to build it yourself :-)

to add the repository
sudo apt-add-repository ppa:costamagnagianfranco/locutusofborg-ppa
sudo apt-get update
sudo apt-get install virtualbox (or upgrade)

[Bill Ataras (signalman)]

Thanks for what appears to be the solution. It installed without any
grief, and I've been using vbox for about 2 hours without any problems.

Only one comment: I looked in my package manager to find the repo you
listed. It appears to be there, but "launchpad.net" is in the link
address right after "ppa:" I assume that this doesn't suggest a problem
of some kind.

Bill

On 12/16/2014 02:07 AM, LocutusOfBorg wrote:
> Hi Bill, the patch was useful to me, to upload a fixed version into my ppa.
> Now if you can test the ppa and report back positive feedbacks I'll ask a sponsor to make the fix be uploaded into the ubuntu repositories.
>
> there is no more need to build it yourself :-)
>
> to add the repository
> sudo apt-add-repository ppa:costamagnagianfranco/locutusofborg-ppa
> sudo apt-get update
> sudo apt-get install virtualbox (or upgrade)
>

--
Bill Ataras

[Gianfranco Costamagna (costamagnagianfranco)]

yes, the solution was to issue some sort of apt-add-repository ppa:costamagnagianfranco/locutusofborg-ppa.

Anyway, I hope somebody will sponsor the patch into ubuntu archives soon.

thanks for testing

[Daniel Holbach (dholbach)]

Upload is sitting in the queue now: https://launchpad.net/ubuntu/precise/+queue?queue_state=1&queue_text=

[Brian Murray (brian-murray)]

Hello Jason, or anyone else affected,

Accepted virtualbox into precise-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/virtualbox/4.1.12-dfsg-2ubuntu0.7 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!

[Neal McBurnett (nealmcb)]

I'm running precise with the Trusty HWE. I just installed the latest from proposed - virtualbox 4.1.12-dfsg-2ubuntu0.7
It seems to have loaded up find after a reboot, and I could start up a VM. Thanks!

[Launchpad Janitor (janitor)]

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

[Brian Murray (brian-murray)]

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.

[Launchpad Janitor (janitor)]

This bug was fixed in the package virtualbox - 4.1.12-dfsg-2ubuntu0.7

---------------
virtualbox (4.1.12-dfsg-2ubuntu0.7) precise; urgency=low

  * Add support for VirtualBox host kernel modules on Linux 3.13
    (LP: #1292118).
 -- Corey Wright <email address hidden> Sun, 14 Dec 2014 18:58:12 -0600

[josagal (josagal8)]

Someone here told me to update with -proposed repository- to fix the virtualbox problem. Now I remember why I did uncheck that repo, everytime I open Chromium, I get a black screen since it installed the new kernel 3.13.0-44-generic #73~precise1-Ubuntu.