virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module failed to build [merge request]

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

I added a fixed package here: ppa:bobby-prani/virtualbox-precise

The attachment "38-fix-for-3.5-kernel.patch" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-reviewers team please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]

Could you confirm if the new packages in the ppa solve the issue?

Hello,
I've updated the virtual box package via the provided ppa. The update was successfull. The kernel module finished build successfully.

Sorry for the delay, I was offline on an excursion for a few days.
Thanks for your support, I did something different:

I got the virtualbox deb sources directly from oracle and inserted them
in apt. Then I installed the virtualbox-4.2 package which works flawlessly.

Cheers Philipp

Am 28.11.2012 03:43, schrieb pranith:
> Could you confirm if the new packages in the ppa solve the issue?
>

PPA fix checked. Module building OK confirmed.

Module building: "[ OK ]". Confirmed.

The status "fix committed" is incorrect as no package has been uploaded into ubuntu official archive to solve this problem.
The proposed patch needs to be converted into a debdiff, or a correct packaging branch merge proposal needs to be made with correct debian/changelog, etc.

This fix should land in Raring first (unless that is working correctly already), before landing in Quantal.
Please follow https://wiki.ubuntu.com/StableReleaseUpdates guidelines and update the bug report suitable for stable release update.

This is already fixed in raring.
I've uploaded fixes for precise and quantal-proposed a few weeks ago.
They are still pending in the SRU review queue.

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

Quoting debfx:
> This is already fixed in raring.
> I've uploaded fixes for precise and quantal-proposed a few weeks ago.
> They are still pending in the SRU review queue.

@debfx: are we still waiting for those?
I don't see them in the pending SRU queue...
http://people.canonical.com/~ubuntu-archive/pending-sru.html

Why is this not yet fixed? I see a ton of bug reports lately for the same exact problem. Please release the fix asap! Thanks

@ pranith:

I've undupped bug1108097 since you've not asked the dev's to update the package to a higher version, which is preffered but not possible due to the very strict debian rules (you can follow the conversation there):

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691148

So your bug is different from the one I had placed, since it regards in special higher versions of Ubuntu too. Don't forget Ubuntu is debianbased.

The Debian PTS tells me it's in Experimental (there):

http://packages.qa.debian.org/v/virtualbox.html

Changelog:

http://packages.debian.org/changelogs/pool/main/v/virtualbox/virtualbox_4.1.18-dfsg-2.1/changelog

Just change the title of this report to [merge request]

Raring is = 4.1.22
Quantal = 4.1.18
Precise = 4.1.12

Keeping in mind that the Ubunutu packages differ from Debian's

How do we ping/prod the maintainer to release fixed packages? New bugs are coming in almost every day now...

hi! pranith

It is always possible to get in touch with the Ubuntu-Developers via:

https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel

the mailing-list or IRC

The preferred way is anyway to apply a patch that comes from upstream:

https://www.virtualbox.org/ticket/11035

And:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55940

Even though kernel.org recommends to run a linux-distro with the newest stable kernel, this is not possible with some packages installed in Ubuntu that need own Kernel modules.

You could ask why the patch from

http://packages.debian.org/changelogs/pool/main/v/virtualbox/virtualbox_4.1.18-dfsg-2.1/changelog

hasn't been adopted to Virtualbox 4.1.12 (12.04.2) and why the merge from Debian hasn't happend yet. This possibly refers back to the freezed status of Debians Wheezy.

My personal solution is to use the newest package (4.2.6) from VirtualBox.org since I don't want to miss out the other bugfixes and enhancements the programm has to offer. Also I need to use USB 2.0 therefore I also installed the closed source "extension-pack" and use VirtualBox with the PUEL-Licence. And that since many years...

I would consider applying the patch here instead of upgrading to a higher version, since that entails lot more work and the problems highlighted above. Comments?

Then follow the instructions on comment#11 in this thread otherwise there is nothing going to happen. Did you overead it?

yes, I mailed on ubuntu-devel-discuss and the mail is waiting approval.

https://wiki.ubuntu.com/StableReleaseUpdates

I propose to use the patch from #3, but refresh it against the current sources. Then use dkms.conf to apply it to 3.5 only. This will not cause regressions with the 3.2 Precise kernel for sure, but it allows the currently broken quantal lts kernel to build.

As a quick hack, I downloaded the patch to /etc/dkms/ and post-processed it to allow DKMS to accept the patch:

    sed 's,/src/VBox/Runtime,,' 38-fix-for-3.5-kernel.patch -i

Next, I created /etc/dkms/virtualbox.conf containing:

    PATCH[0]=../../../../../../../../../../../../../../etc/dkms/38-fix-for-3.5-kernel.patch
    PATCH_MATCH[0]=^3.5
(the definitive fix for ubuntu should put the patch in /usr/src/virtualbox-*/patches which allows the ../...../etc/dkms/ part to be stripped)

Result:
# dkms -m virtualbox -v 4.1.12 install

Kernel preparation unnecessary for this kernel. Skipping...

Building module:
cleaning build area...
Kernel preparation unnecessary for this kernel. Skipping...
applying patch ../../../../../../../../../../../../../../etc/dkms/38-fix-for-3.5-kernel.patch...patching file r0drv/linux/memobj-r0drv-linux.c
Hunk #3 succeeded at 524 (offset -1 lines).
Hunk #4 succeeded at 592 (offset -1 lines).
Hunk #5 succeeded at 613 (offset -1 lines).
Hunk #6 succeeded at 1204 (offset -9 lines).
Hunk #7 succeeded at 1221 (offset -9 lines).
Hunk #8 succeeded at 1415 (offset -9 lines).
Hunk #9 succeeded at 1427 (offset -9 lines).
Hunk #10 succeeded at 1511 (offset -9 lines).
Hunk #11 succeeded at 1528 (offset -9 lines).
patching file r0drv/linux/the-linux-kernel.h
[...]
DKMS: build completed.

vboxdrv.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/3.5.0-25-generic/updates/dkms/

vboxnetadp.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/3.5.0-25-generic/updates/dkms/

vboxnetflt.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/3.5.0-25-generic/updates/dkms/

vboxpci.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/3.5.0-25-generic/updates/dkms/

depmod....

DKMS: install completed.

how do i install this patch??????

pragna, use this ppa to install: https://launchpad.net/~bobby-prani/+archive/virtualbox-precise

I get a message saying couldn't find a suitable CD after i add then to the
software sources and add volume

On Fri, Mar 8, 2013 at 7:59 PM, pranith <email address hidden> wrote:

> pragna, use this ppa to install: https://launchpad.net/~bobby-
> prani/+archive/virtualbox-precise
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1152398).
> https://bugs.launchpad.net/bugs/1081307
>
> Title:
> virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module
> failed to build [merge request]
>
> Status in “virtualbox” package in Ubuntu:
> Fix Released
> Status in “virtualbox” source package in Precise:
> In Progress
> Status in “virtualbox” source package in Quantal:
> In Progress
> Status in “virtualbox” source package in Raring:
> Fix Released
>
> Bug description:
> I'm using aptitude as a packet manager.
>
> ProblemType: Package
> DistroRelease: Ubuntu 12.04
> Package: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2
> ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
> Uname: Linux 3.2.0-32-generic x86_64
> NonfreeKernelModules: nvidia
> ApportVersion: 2.0.1-0ubuntu15
> Architecture: amd64
> DKMSKernelVersion: 3.5.0-18-generic
> Date: Tue Nov 20 23:13:23 2012
> InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
> (20120425)
> MarkForUpload: True
> PackageArchitecture: all
> PackageVersion: 4.1.12-dfsg-2ubuntu0.2
> SourcePackage: virtualbox
> Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module
> failed to build
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> [Impact]
> Users are not able to use virtualbox from the repository on 12.04 with
> 3.5 kernel. It is totally broken.
> The patch proposed backports only the relevant parts from upstream to
> fix the bug.
> The patch is from: https://www.virtualbox.org/changeset/41660/vbox
>
> [Test Case]
> Upgrade to 3.5 kernel on 12.04 and install virtualbox.
>
> [Regression Potential]
> It is best to use the latest upstream version. But since that will cause
> major disruption, we have to track this package and corresponding bugs for
> regressions.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1081307/+subscriptions
>

FYI: Raring was equipped with VirtualBox 4.2.8 (a few hours ago)

https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1101867/comments/21

Looks like this is already fixed in Quantal. I'll do some testing with the Precise package and put it on the sponsoring queue now.

I can confirm the packages of the ppa in #29 are working ok and the modules are compiled with no errors in 12.04.2

Can anyone replace the virtualbox packages for precise with the ones from this ppa? If so we would get the bug fixed in precise 12.04.2

Running Ubuntu 12.04.2 LTS 64 bit on Windows XP 32 bit. When installing with the patch in #29 I am getting a bit further but compiling stops at

  CC [M] /var/lib/dkms/virtualbox-guest/4.1.12/build/vboxsf/vfsmod.o
/var/lib/dkms/virtualbox-guest/4.1.12/build/vboxsf/vfsmod.c: In function ‘sf_evict_inode’:
/var/lib/dkms/virtualbox-guest/4.1.12/build/vboxsf/vfsmod.c:376:5: error: implicit declaration of function ‘end_writeback’ [-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
make[2]: *** [/var/lib/dkms/virtualbox-guest/4.1.12/build/vboxsf/vfsmod.o] Error 1
make[1]: *** [/var/lib/dkms/virtualbox-guest/4.1.12/build/vboxsf] Error 2
make: *** [_module_/var/lib/dkms/virtualbox-guest/4.1.12/build] Error 2
make: Leaving directory `/usr/src/linux-headers-3.5.0-26-generic'

@Johan could you try the ppa in comment #29 and see if that works?

Confirmed the ppa in Comment #29 allows me to get virtualbox back up and running after installing the lts-quantal kernel and xserver, moving me from 12.04.1 to 12.04.2.

Confirming the same error that johan-ehnberg reported.
Host OS is Quantal 64-bit, guest is Precise (Ubuntu 12.04.2 LTS) 64-bit.
After adding the ppa from comment#29 to the guest, building the kernel modules fails with error as shown in #34.

@whyscream could you report the kernel version you are using? please run "apport-collect 1081307"

The apport-collect command exited with:

Package virtualbox not installed and no hook available, ignoring
*** Updating problem report
No additional information collected.

Anyway, kernel is:
ii linux-image-3.5.0-26-generic 3.5.0-26.42~precise1 Linux kernel image for version 3.5.0 on 64 bit x86 SMP

And vbox packages are:
ii virtualbox-guest-dkms 4.1.12-dfsg-2ubuntu1 x86 virtualization solution - guest addition module source for dkms
ii virtualbox-guest-utils 4.1.12-dfsg-2ubuntu1 x86 virtualization solution - non-X11 guest utilities
ii virtualbox-guest-x11 4.1.12-dfsg-2ubuntu1 x86 virtualization solution - X11 guest utilities
(from ppa)

Check if you removed the virtualbox install. Run "apt-get remove virtualbox" and then add the ppa.

@ruben-silvarocha: there never was a virtualbox package in the guest, only the listed guest packages. While I tried various variants (default packages in guest, manual install from mounted virtualbox-guest-additions-iso from host, ppa packages), all of the packages were removed using 'apt-get purge' before trying new ones.

Hello Radoslav, or anyone else affected,

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

It is working fine here with the package from precise-proposed.

Thanks for the fix.

I can also confirm that virtualbox-dkms/precise-proposed works fine for both 3.2 and 3.5 kernel. I will attach the output of `dpkg-reconfigure virtualbox-dkms`.

Confirmed again: works as expected

The package from -proposed works for me.

Virtual box guest extensions work fine after installing the packages from
"precise-proposed".
On Apr 2, 2013 2:21 PM, "Brian Murray" <email address hidden> wrote:

> Hello Radoslav, or anyone else affected,
>
> Accepted virtualbox into precise-proposed. The package will build now
> and be available at
> http://launchpad.net/ubuntu/+source/virtualbox/4.1.12-dfsg-2ubuntu0.3 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!
>
> ** Changed in: virtualbox (Ubuntu Precise)
> Status: In Progress => Fix Committed
>
> ** Tags added: verification-needed
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1158426).
> https://bugs.launchpad.net/bugs/1081307
>
> Title:
> virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module
> failed to build [merge request]
>
> Status in “virtualbox” package in Ubuntu:
> Fix Released
> Status in “virtualbox” source package in Precise:
> Fix Committed
> Status in “virtualbox” source package in Quantal:
> Fix Released
> Status in “virtualbox” source package in Raring:
> Fix Released
>
> Bug description:
> I'm using aptitude as a packet manager.
>
> ProblemType: Package
> DistroRelease: Ubuntu 12.04
> Package: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2
> ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
> Uname: Linux 3.5.0-26-generic x86_64
> NonfreeKernelModules: nvidia
> ApportVersion: 2.0.1-0ubuntu15
> Architecture: amd64
> DKMSKernelVersion: 3.5.0-18-generic
> Date: Tue Nov 20 23:13:23 2012
> InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
> (20120425)
> MarkForUpload: True
> PackageArchitecture: all
> PackageVersion: 4.1.12-dfsg-2ubuntu0.2
> SourcePackage: virtualbox
> Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module
> failed to build
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> [Impact]
> Users are not able to use virtualbox from the repository on 12.04 with
> 3.5 kernel. It is totally broken.
> The patch proposed backports only the relevant parts from upstream to
> fix the bug.
> The patch is from: https://www.virtualbox.org/changeset/41660/vbox
>
> [Test Case]
> Upgrade to 3.5 kernel on 12.04 and install virtualbox.
>
> [Development Fix]
> Fixed during Quantal cycle.
>
> [Stable Fix]
> Is being fixed in 4.1.12-dfsg-2ubuntu0.3 upload to prec...

The proposed package works for me as well.

Does not work for me. I added -proposed to repositories. i had previously
removed all trace of virtual box.

I then did sudo apt-get update
Then I did sudo apt-get install virtualbox/precise-propsed

VB then appeared to come up at all. I tried importing a VB machine that
runs fine on 5 other machines here (but under U 10.04). No go - it didn't
like the extension pack.
So I tried the other available one at Oracle.

Now, partway through booting up windows, it simply crashes Ubuntu - hard
crash, back to bios. Whatever this fix is, maybe I'm missing something,
but crashing is WORSE than merely tossing an error and refusing to run. At
least it's a first - 10.04 hasn't crashed in 6-7 machines ever...in all
those years of daily use.

On Mon, Apr 8, 2013 at 3:51 PM, Jeff Weston <email address hidden> wrote:

> The proposed package works for me as well.
>
> ** Attachment added: "Installation Output.txt"
>
> https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1081307/+attachment/3632139/+files/Installation%20Output.txt
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1165520).
> https://bugs.launchpad.net/bugs/1081307
>
> Title:
> virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module
> failed to build [merge request]
>
> Status in “virtualbox” package in Ubuntu:
> Fix Released
> Status in “virtualbox” source package in Precise:
> Fix Committed
> Status in “virtualbox” source package in Quantal:
> Fix Released
> Status in “virtualbox” source package in Raring:
> Fix Released
>
> Bug description:
> I'm using aptitude as a packet manager.
>
> ProblemType: Package
> DistroRelease: Ubuntu 12.04
> Package: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2
> ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
> Uname: Linux 3.5.0-26-generic x86_64
> NonfreeKernelModules: nvidia
> ApportVersion: 2.0.1-0ubuntu15
> Architecture: amd64
> DKMSKernelVersion: 3.5.0-18-generic
> Date: Tue Nov 20 23:13:23 2012
> InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
> (20120425)
> MarkForUpload: True
> PackageArchitecture: all
> PackageVersion: 4.1.12-dfsg-2ubuntu0.2
> SourcePackage: virtualbox
> Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module
> failed to build
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> [Impact]
> Users are not able to use virtualbox from the repository on 12.04 with
> 3.5 kernel. It is totally broken.
> The patch proposed backports only the relevant parts from upstream to
> fix the bug.
> The patch is from: https://www.virtualbox.org/changeset/41660/vbox
>
> [Test Case]
> Upgrade to 3.5 kernel on 12.04 and install virtualbox.
>
> [Development Fix]
> Fixed during Quantal cycle.
>
> [Stable Fix]
> Is being fixed in 4.1.12-dfsg-2ubuntu0.3 upload to precise-proposed.
>
> [Regression Potential]
> It is best to use the latest upstream version. But since that will cause
> major disruption, we have to track this package and corresponding bugs for
> regressions.
>
> jamespage: Please also check backwards compatibility with the 3.2
> kernel; the patch shoul...

I got an error when trying to install VirtualBox using this command:

$ sudo apt-get install virtualbox/precise-propsed

However, it installed correctly and I was able to run a virtual machine
when I installed VirtualBox using this command:

$ sudo apt-get install virtualbox-dkms/precise-proposed

On Mon, Apr 8, 2013 at 2:24 PM, Doug Coulter <email address hidden> wrote:

> Does not work for me. I added -proposed to repositories. i had previously
> removed all trace of virtual box.
>
> I then did sudo apt-get update
> Then I did sudo apt-get install virtualbox/precise-propsed
>
> VB then appeared to come up at all. I tried importing a VB machine that
> runs fine on 5 other machines here (but under U 10.04). No go - it didn't
> like the extension pack.
> So I tried the other available one at Oracle.
>
> Now, partway through booting up windows, it simply crashes Ubuntu - hard
> crash, back to bios. Whatever this fix is, maybe I'm missing something,
> but crashing is WORSE than merely tossing an error and refusing to run. At
> least it's a first - 10.04 hasn't crashed in 6-7 machines ever...in all
> those years of daily use.
>
>
> On Mon, Apr 8, 2013 at 3:51 PM, Jeff Weston <email address hidden> wrote:
>
> > The proposed package works for me as well.
> >
> > ** Attachment added: "Installation Output.txt"
> >
> >
> https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1081307/+attachment/3632139/+files/Installation%20Output.txt
> >
> > --
> > You received this bug notification because you are subscribed to a
> > duplicate bug report (1165520).
> > https://bugs.launchpad.net/bugs/1081307
> >
> > Title:
> > virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module
> > failed to build [merge request]
> >
> > Status in “virtualbox” package in Ubuntu:
> > Fix Released
> > Status in “virtualbox” source package in Precise:
> > Fix Committed
> > Status in “virtualbox” source package in Quantal:
> > Fix Released
> > Status in “virtualbox” source package in Raring:
> > Fix Released
> >
> > Bug description:
> > I'm using aptitude as a packet manager.
> >
> > ProblemType: Package
> > DistroRelease: Ubuntu 12.04
> > Package: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2
> > ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
> > Uname: Linux 3.5.0-26-generic x86_64
> > NonfreeKernelModules: nvidia
> > ApportVersion: 2.0.1-0ubuntu15
> > Architecture: amd64
> > DKMSKernelVersion: 3.5.0-18-generic
> > Date: Tue Nov 20 23:13:23 2012
> > InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
> > (20120425)
> > MarkForUpload: True
> > PackageArchitecture: all
> > PackageVersion: 4.1.12-dfsg-2ubuntu0.2
> > SourcePackage: virtualbox
> > Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module
> > failed to build
> > UpgradeStatus: No upgrade log present (probably fresh install)
> >
> > [Impact]
> > Users are not able to use virtualbox from the repository on 12.04 with
> > 3.5 kernel. It is totally broken.
> > The patch proposed backports only the relevant parts from upstream to
> > fix the bug.
> > The patch is from: https://www.virtualbox.org/changeset/41660/vbox
> >
> >...

@Doug The problem with the guest system sounds like a different bug. Maybe related to the guest-additions? Did you ever get your guests to run in VirtualBox on Ubuntu Precise with Linux-kernel 3.2.0-xx ?

No. Frankly, I've avoided upgrading to precise as long as I could as I
detest the new desktop (along with the huge majority of real old timer
computer devs/users). Now that there's Mate, I'm moving a few machines
over to get the new kernel etc. This is a new-build machine, so I had to
use 12.04/64 to get past the UEFI issues. I'd just as soon be using 32
bit, sigh, but had to go with the UEFI flow, you know.

I tried the advice above - using sudo apt-get install
virtualbox-dkms/precise-
proposed

Which removed VB 4.2 and put in 4.1.something. I don't care about that one
- I am not "stressing" VB much here - just using it to run windows to run
some lab tools that aren't compatible with linux (for my mass spectrometer
and suchlike, which barely run on windows, no hope in wine, and some of my
uP dev ide's for things like PIC uPs I write code for.)
.
Trying virtualbox from a terminal gives me an error - "Error opening file
for reading: permission denied (when run as me). It doesn't get this error
running as sudo but...
It still crashes during *any* VM bootup - all the way back to my bios.
(Glad I have an SSD, I've never ever had to reboot linux at all, much less
6 times an hour).
Doesn't matter about what VM I try to boot - Xp or Win7, several versions,
& re-import the "appliance" on every try (they get internally corrupted on
the attempt that fails). I did add the extension pack suitable for this
version of VB since those images do use USB.

Since the thing won't boot an image at all - kills the entire machine
partway through, I've not been able to install/update the guest additions
on these images...This is a real show stopper here - I'd hate to kick off
linux and have to build a windows-only box, but my physics lab has to
run...(www.coultersmithing.com/forums)

Precise is not making me at all happy. VB does work on machines I
"upgraded" that had it already, but not on this new build. The thing is, a
fusor sometimes fries a nearby data aq PC - so I need to keep making more
machines now and again...(something about a 100kv power supply arcing and
making gigawatt emp - despite shielding, sometimes fries a mobo). This
machine is intended to be ready for when the one in service has that happen
to it.

I can't get 10.04 to install at all on a UEFI mobo, even trying my best to
turn the UEFI junk off in the bios (ASUS P8H 77-M/i5/8gig ram).

Is there anything else I can use that will import .ova files? I'm not wed
to VB or especially anything oracle...just need something that'll get my
job done.

On Mon, Apr 8, 2013 at 5:49 PM, Andre <email address hidden> wrote:

> @Doug The problem with the guest system sounds like a different bug.
> Maybe related to the guest-additions? Did you ever get your guests to
> run in VirtualBox on Ubuntu Precise with Linux-kernel 3.2.0-xx ?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1165520).
> https://bugs.launchpad.net/bugs/1081307
>
> Title:
> virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module
> failed to build [merge request]
>
> Status in “virtualbox” package in Ubuntu:
> Fix Released
> Status in “virtualbox” source package...

Στις 09/04/2013 01:48 πμ, ο/η Doug Coulter έγραψε:
> Precise is not making me at all happy. VB does work on machines I
> "upgraded" that had it already, but not on this new build.

If you install linux-image-generic-pae (3.2.0.39.47), the one that
12.04.1 had, and boot your system with it, and virtualbox still doesn't
run, then it's another issue, not the one described in this bug.

This bug report is about a regression from 12.04.1 to 12.04.2+.

Although I've already put some days of work into building this system up -
I'll try that if I can find an old distro version - I've got to get this
working doggone it. I never said this was the same bug - the
devs/maintainers said that and moved my report.
(Not that I was cool enough to do full research - I just submitted an
automatic bug report)

On Mon, Apr 8, 2013 at 10:27 PM, Alkis Georgopoulos <
<email address hidden>> wrote:

> Στις 09/04/2013 01:48 πμ, ο/η Doug Coulter έγραψε:
> > Precise is not making me at all happy. VB does work on machines I
> > "upgraded" that had it already, but not on this new build.
>
> If you install linux-image-generic-pae (3.2.0.39.47), the one that
> 12.04.1 had, and boot your system with it, and virtualbox still doesn't
> run, then it's another issue, not the one described in this bug.
>
> This bug report is about a regression from 12.04.1 to 12.04.2+.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1165520).
> https://bugs.launchpad.net/bugs/1081307
>
> Title:
> virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module
> failed to build [merge request]
>
> Status in "virtualbox" package in Ubuntu:
> Fix Released
> Status in "virtualbox" source package in Precise:
> Fix Committed
> Status in "virtualbox" source package in Quantal:
> Fix Released
> Status in "virtualbox" source package in Raring:
> Fix Released
>
> Bug description:
> I'm using aptitude as a packet manager.
>
> ProblemType: Package
> DistroRelease: Ubuntu 12.04
> Package: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2
> ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
> Uname: Linux 3.5.0-26-generic x86_64
> NonfreeKernelModules: nvidia
> ApportVersion: 2.0.1-0ubuntu15
> Architecture: amd64
> DKMSKernelVersion: 3.5.0-18-generic
> Date: Tue Nov 20 23:13:23 2012
> InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
> (20120425)
> MarkForUpload: True
> PackageArchitecture: all
> PackageVersion: 4.1.12-dfsg-2ubuntu0.2
> SourcePackage: virtualbox
> Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module
> failed to build
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> [Impact]
> Users are not able to use virtualbox from the repository on 12.04 with
> 3.5 kernel. It is totally broken.
> The patch proposed backports only the relevant parts from upstream to
> fix the bug.
> The patch is from: https://www.virtualbox.org/changeset/41660/vbox
>
> [Test Case]
> Upgrade to 3.5 kernel on 12.04 and install virtualbox.
>
> [Development Fix]
> Fixed during Quantal cycle.
>
> [Stable Fix]
> Is being fixed in 4.1.12-dfsg-2ubuntu0.3 upload to precise-proposed.
>
> [Regression Potential]
> It is best to use the latest upstream version. But since that will cause
> major disruption, we have to track this package and corresponding bugs for
> regressions.
>
> jamespage: Please also check backwards compatibility with the 3.2
> kernel; the patch should support this but best to make sure (not all
> 12.04 installs with have 3.5).
>
> To manage notifications about this bug go...

@Doug I've had a good experience with uninstalling Virtualbox packages that come from the Ubuntu repositories and instead getting Virtualbox directly from virtualbox.org's repository for Ubuntu.

Instructions: http://www.itworld.com/virtualization/308757/install-virtualbox-424-ubuntu-1204-or-1210

Works well for me even on 12.04.2 with the new kernel and it means you always have the latest Virtualbox version.

I tried that too, no good (4.2.x, using the directions on the oracle site -
these are a little different, so something new to try) but I've not tried
every possible combination yet - only about 10 permutations so far
(speaking of frustration). When I tried the -proposed, it took the stuff
straight from oracle out and substituted 4.1.x during the install process.
I'd been doing the straight from oracle thing on 10.04 mostly, but not
upgrading everytime it asked, since that was causing my win-7 DRM to kick
in (till I got and used a key-cracker). That stank as I've paid for win7
twice and couldn't even run it at all after I upgraded VB - it detected a
"hardware change" on the upgrade and decided I'd stolen it.
So now I AM running a stolen iso with a key cracker, once, to get what I
paid for twice, on the 5-6 machines that *do not* run 12.04. Last night
the 12,.04 machine grabbed a new kernal, so now I get to try all this again
I suppose, but for now - it still does not work and even crashes linux back
to bios, with the usual bad effects on things like mail and web program
context for unexpected crashes (my own running code doesn't have issues
with sudden crashes since I wrote it with that expectation, it's an edge
case that gets hit here due to arcs in nearby HV supplies). Ugh.

To clarify - the other above suggestions did let me install VB "at all",
and import an image - but all images crash during boot, before the main
screen shows up, usually. I once had win7 show me the login, but logging
in - boom, it crashed, then linux went down.

Could it matter that since I have plenty ram (8g) for what I use this for,
I didn't put in a swap partition? I've never had an issue with that
before, other than the linux install kinda whining when I don't. Since I'm
running a combo of SSD and spinner - I put / on the SSD, but /home and /tmp
on a spinner to prolong SSD life.

Doug

On Tue, Apr 9, 2013 at 5:56 AM, Tim Edwards <email address hidden>wrote:

> @Doug I've had a good experience with uninstalling Virtualbox packages
> that come from the Ubuntu repositories and instead getting Virtualbox
> directly from virtualbox.org's repository for Ubuntu.
>
> Instructions: http://www.itworld.com/virtualization/308757/install-
> virtualbox-424-ubuntu-1204-or-1210
>
> Works well for me even on 12.04.2 with the new kernel and it means you
> always have the latest Virtualbox version.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1165520).
> https://bugs.launchpad.net/bugs/1081307
>
> Title:
> virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module
> failed to build [merge request]
>
> Status in “virtualbox” package in Ubuntu:
> Fix Released
> Status in “virtualbox” source package in Precise:
> Fix Committed
> Status in “virtualbox” source package in Quantal:
> Fix Released
> Status in “virtualbox” source package in Raring:
> Fix Released
>
> Bug description:
> I'm using aptitude as a packet manager.
>
> ProblemType: Package
> DistroRelease: Ubuntu 12.04
> Package: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2
> ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
> Uname: L...

When will this fix be released for precise? (considering it is an important and old bug)

Yes, I either have a different bug, or this isn't the real fix. I've tried
every combo in the thread above, and on a new install of 12.04, no go - I
did get as far as getting an error free install of VB, but then every
windows virtual machine crashes - and crashes linux itself - halfway
through a boot - right at that "booting windows" screen, before the login.

On Mon, Apr 15, 2013 at 12:10 PM, Ads20000 <email address hidden>wrote:

> When will this fix be released for precise? (considering it is an
> important and old bug)
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1165520).
> https://bugs.launchpad.net/bugs/1081307
>
> Title:
> virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module
> failed to build [merge request]
>
> Status in “virtualbox” package in Ubuntu:
> Fix Released
> Status in “virtualbox” source package in Precise:
> Fix Committed
> Status in “virtualbox” source package in Quantal:
> Fix Released
> Status in “virtualbox” source package in Raring:
> Fix Released
>
> Bug description:
> I'm using aptitude as a packet manager.
>
> ProblemType: Package
> DistroRelease: Ubuntu 12.04
> Package: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2
> ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
> Uname: Linux 3.5.0-26-generic x86_64
> NonfreeKernelModules: nvidia
> ApportVersion: 2.0.1-0ubuntu15
> Architecture: amd64
> DKMSKernelVersion: 3.5.0-18-generic
> Date: Tue Nov 20 23:13:23 2012
> InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
> (20120425)
> MarkForUpload: True
> PackageArchitecture: all
> PackageVersion: 4.1.12-dfsg-2ubuntu0.2
> SourcePackage: virtualbox
> Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module
> failed to build
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> [Impact]
> Users are not able to use virtualbox from the repository on 12.04 with
> 3.5 kernel. It is totally broken.
> The patch proposed backports only the relevant parts from upstream to
> fix the bug.
> The patch is from: https://www.virtualbox.org/changeset/41660/vbox
>
> [Test Case]
> Upgrade to 3.5 kernel on 12.04 and install virtualbox.
>
> [Development Fix]
> Fixed during Quantal cycle.
>
> [Stable Fix]
> Is being fixed in 4.1.12-dfsg-2ubuntu0.3 upload to precise-proposed.
>
> [Regression Potential]
> It is best to use the latest upstream version. But since that will cause
> major disruption, we have to track this package and corresponding bugs for
> regressions.
>
> jamespage: Please also check backwards compatibility with the 3.2
> kernel; the patch should support this but best to make sure (not all
> 12.04 installs with have 3.5).
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1081307/+subscriptions
>

--
Why guess when you can know. Measure!

@Ads20000,

other targets of this SRU, Bug #1031217, Bug #1071344, are waiting to be verified.

I switched to proposed source and it solved the problem. But now I cannot install virtualbox-guest-x11 package because it depends on old version of virtualbox-guest-utils package.

I confirm that the packages in ppa:bobby-prani/virtualbox-precise solved the problem.

@vafsr There are already fixed/updated packages in the "proposed" repository. Please take a look at comment #42 on how to enable proposed and install the packages.

The proposed changes allowed me to install VirtualBox and for it to build
successfully, however, every Virtual Machine crashes not only itself but Li
ux itself when you try to boot one. These virtual machines work everywhere
else. There's still a major bug.

On Apr 29, 2013 4:51 PM, "Andre" <email address hidden> wrote:
>
> @vafsr There are already fixed/updated packages in the "proposed"
> repository. Please take a look at comment #42 on how to enable proposed
> and install the packages.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1165520).
> https://bugs.launchpad.net/bugs/1081307
>
> Title:
> virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module
> failed to build [merge request]
>
> Status in “virtualbox” package in Ubuntu:
> Fix Released
> Status in “virtualbox” source package in Precise:
> Fix Committed
> Status in “virtualbox” source package in Quantal:
> Fix Released
> Status in “virtualbox” source package in Raring:
> Fix Released
>
> Bug description:
> I'm using aptitude as a packet manager.
>
> ProblemType: Package
> DistroRelease: Ubuntu 12.04
> Package: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2
> ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
> Uname: Linux 3.5.0-26-generic x86_64
> NonfreeKernelModules: nvidia
> ApportVersion: 2.0.1-0ubuntu15
> Architecture: amd64
> DKMSKernelVersion: 3.5.0-18-generic
> Date: Tue Nov 20 23:13:23 2012
> InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
(20120425)
> MarkForUpload: True
> PackageArchitecture: all
> PackageVersion: 4.1.12-dfsg-2ubuntu0.2
> SourcePackage: virtualbox
> Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module
failed to build
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> [Impact]
> Users are not able to use virtualbox from the repository on 12.04 with
3.5 kernel. It is totally broken.
> The patch proposed backports only the relevant parts from upstream to
fix the bug.
> The patch is from: https://www.virtualbox.org/changeset/41660/vbox
>
> [Test Case]
> Upgrade to 3.5 kernel on 12.04 and install virtualbox.
>
> [Development Fix]
> Fixed during Quantal cycle.
>
> [Stable Fix]
> Is being fixed in 4.1.12-dfsg-2ubuntu0.3 upload to precise-proposed.
>
> [Regression Potential]
> It is best to use the latest upstream version. But since that will
cause major disruption, we have to track this package and corresponding
bugs for regressions.
>
> jamespage: Please also check backwards compatibility with the 3.2
> kernel; the patch should support this but best to make sure (not all
> 12.04 installs with have 3.5).
>
> To manage notifications about this bug go to:
>
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1081307/+subscriptions

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

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

  [ Felix Geyer ]
  * Fix build errors with kernel 3.5. (LP: #1081307)
    - Add 39-kernel-35.patch
  * Fix crash when running 64-bit guests on a 32-bit host system.
    (LP: #1071344)
    - Add 40-fix-crash-64bit-guests.patch
  * Fix broken DNS in guests when the NetworkManager dnsmasq resolver
    is used on the host. (LP: #1031217)
    - Add 38-fix-nat-local-dns-resolver.patch

  [ Dmitry Shachnev ]
  * Fix the changelog, refresh patches and re-upload to precise-proposed.
 -- Felix Geyer <email address hidden> Sun, 31 Mar 2013 19:01:17 +0200

The verification of this Stable Release Update 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 regresssions.

Sadly, while this did fix the build bug (as did the -proposed), I still
have a major bug - VB is totally unusable on 12.04 with any guest I have
(all of which work on every other machine here). Partway through booting,
say, 32 bit winxp - linux crashes and restarts.
(all my appliances are windows/32)

These are 32 bit appliances trying to run on a 12.04 that is 64 bit, i5, 8
gigs ram, SSD and spinners. They do run fine on 32 bit 12.04's that were
upgraded from 10.04, but not on this fresh build that required 64 bit to
get past the UEFI mobo - 32 bit ubuntu would not install, so I went 64, as
recommended on this box.

These machines also run fine on an upgraded 10.04/64 bit other machine.

My bug report was assigned to this bug as a dupe, but it isn't a dupe and
doesn't belong on this thread. How do I report this as a bug of its own?
It is NOT the same one.

This only appears to happen on a fresh install of 12.04 - not on ones
upgraded from 10.04. So there's something important that is different
between a fresh install and an upgrade.

Yes, despite it being hard on 12.04, I added my user to all the right
groups (think, get mate so you can still have a bit of control over your
machine).

On Wed, May 8, 2013 at 10:45 AM, Scott Kitterman <email address hidden>wrote:

> The verification of this Stable Release Update 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 regresssions.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1165520).
> https://bugs.launchpad.net/bugs/1081307
>
> Title:
> virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module
> failed to build [merge request]
>
> Status in “virtualbox” package in Ubuntu:
> Fix Released
> Status in “virtualbox” source package in Precise:
> Fix Released
> Status in “virtualbox” source package in Quantal:
> Fix Released
> Status in “virtualbox” source package in Raring:
> Fix Released
>
> Bug description:
> I'm using aptitude as a packet manager.
>
> ProblemType: Package
> DistroRelease: Ubuntu 12.04
> Package: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2
> ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
> Uname: Linux 3.5.0-26-generic x86_64
> NonfreeKernelModules: nvidia
> ApportVersion: 2.0.1-0ubuntu15
> Architecture: amd64
> DKMSKernelVersion: 3.5.0-18-generic
> Date: Tue Nov 20 23:13:23 2012
> InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
> (20120425)
> MarkForUpload: True
> PackageArchitecture: all
> PackageVersion: 4.1.12-dfsg-2ubuntu0.2
> SourcePackage: virtualbox
> Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module
> failed to build
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> [Impact]
> Users are not able to use virtualbox from the repository on 12.04 wit...

I have done a "no change backport" from raring to precise [4.2.10-dfsg-0ubuntu2~precise1~ppa1] in ppa:dirk-computer42/c42-backport

This seems to work for me quite well.
My machines are on linux-image-generic-lts-raring.

Now it works (12.04)!

Is this a concern?

Setting up virtualbox (4.1.18-dfsg-1ubuntu1.2) ...
 * Stopping VirtualBox kernel modules [ OK ]
 * Starting VirtualBox kernel modules * No suitable module for running kernel found
                                                                         [fail]
invoke-rc.d: initscript virtualbox, action "restart" failed.

When is this getting fixed? This still affects users on a fresh install of 12.04.

Sorry, still affects users on 64-bit version of 12.04. I haven't tested 32-bit version.

Failed after kernel upgrade

Still getting this on recent Precise upgrade

Has this really been fixed?

On my machine it works fine now.

Op 25-11-14 om 00:29 schreef Peter D.:
> Has this really been fixed?
>

Still does not work in mine: Ubuntu 12.04 64 bit