virtualbox-ose-modules for 2.6.24-18

Bug #237278 reported by Guillermo Molleda on 2008-06-04
80
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Undecided
Daniel Hahler
virtualbox-ose-modules (Ubuntu)
High
Daniel Hahler

Bug Description

Binary package hint: update-manager

When update-manager change the linux-kernel, virtualbox-ose can't run the virtuality operating systems.

The problem is that exist different virtualbox-ose-modules-2.6.X-Y package for each kernel version.

And in the las update to kernel 2.6.24-18, don't exist in mirror the packages virtualbox-ose-modules-2.6.24-18-* necessary for working with virtualbox.

Thanks you.

ProblemType: Bug
Architecture: i386
Date: Wed Jun 4 08:56:50 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/sbin/synaptic
NonfreeKernelModules: ath_hal
Package: synaptic 0.61ubuntu9
PackageArchitecture: i386
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
SourcePackage: synaptic
Uname: Linux 2.6.24-18-generic i686

Guillermo Molleda (gmolleda) wrote :
gaax (gaax) wrote :

Same error here.

yeah we need a .18 module added...please add :)

Crowler (crowler-gmail) wrote :

Another one with the same problem...

nox (super-moa) wrote :

Same error.
Ubuntu 8.04, kernel 2.6.24-18

tx

w3rt (lolz) wrote :

Yeah I get the same problem, i hope there is a fix soon

luksol (luksol) wrote :

I have the same error

Guillermo Molleda (gmolleda) wrote :

If you need use VirtualBox, you can restart the computer and choice the kernel 2.6.24-17 in the Grub menu.

Other thing, when you install virtualbox-ose, you need install manually too the virtualbox-ose-modules-KERNELversion, here there is other dependency bug.

If you want, you can change the line "default 0" in file /boot/grub/menu.lst to "default 2" and the default kernel will be 2.6.24-17 and virtualbox will go perfectly.

Ronan O'Malley (omalley-ronan) wrote :

same error, need package for kernel 2.6.24-18.

thanks

Chris Wyatt (wyattmeister) wrote :

Did you have proposed updates switched on, maybe that is why all the packages aren't prepared yet, I've switched that off now as a precaution.

Chris Wyatt (wyattmeister) wrote :

Ah, no, looks like it was just a normal update (when I checked through Synaptic), perhaps this was rushed out due to this security threat:
http://news.softpedia.com/news/Kernel-Vulnerability-in-Ubuntu-8-04-LTS-Upgrade-Now-87195.shtml

Sure it won't be long until the other packages catch up.

McB (makkbe) wrote :

A temporary fix, until the package is updated:

sudo apt-get install virtualbox-ose-source
sudo module-assistant update
sudo module-assistant prepare
sudo module-assistant a-i virtualbox-ose
sudo /etc/init.d/vboxdrv restart

Launch VirtualBox, and it should work.

Mike (michaeltubbe) wrote :

Thanks for the fix suggestion, McB. I tried it (based on a blog I found here:

[url]http://mcb.lessthanthree.se/?p=26[/url]

The second to last line seems to expecting a source tarball. Since I didn't install it from source, it doesn't seem to work.

McB (makkbe) wrote :

The virtualbox-ose-source package contains the sources needed to build the modules, and that is the way I got it to work. What does your output say?

Ronan O'Malley (omalley-ronan) wrote :

first line of blog post suggestion differs from suggestion posted here

The one posted here worked a treat for me.

Thanks McB

McB (makkbe) wrote :

Ronan: that it did. Changed it. Thanks for pointing it out. Now, back to topic.

Daniel Hahler (blueyed) on 2008-06-04
Changed in virtualbox-ose:
assignee: nobody → blueyed
importance: Undecided → High
status: New → In Progress
Daniel Hahler (blueyed) on 2008-06-04
Changed in update-manager:
assignee: nobody → blueyed
status: New → Invalid
PedroM (musilekp) wrote :

 Hi McB - I cannot compile it either, this is what I am getting:

{standard input}: Assembler messages:
{standard input}:437: Error: suffix or operands invalid for `pushf'
{standard input}:438: Error: suffix or operands invalid for `pop'
{standard input}:479: Error: suffix or operands invalid for `push'
{standard input}:480: Error: suffix or operands invalid for `popf'
{standard input}:4178: Error: suffix or operands invalid for `mov'
{standard input}:5251: Error: suffix or operands invalid for `mov'
kmk[4]: *** [/usr/src/modules/virtualbox-ose/SUPDRVShared.o] Error 1
kmk[3]: *** [_module_/usr/src/modules/virtualbox-ose] Error 2
kmk[3]: Leaving directory `/usr/src/linux-headers-2.6.24-18-generic'
kmk[2]: *** [vboxdrv] Error 2
kmk[2]: Leaving directory `/usr/src/modules/virtualbox-ose'
kmk[1]: *** [binary-modules] Error 2
kmk[1]: Leaving directory `/usr/src/modules/virtualbox-ose'
make: *** [kdist_build] Error 2

Mike (michaeltubbe) wrote :

Thanks for pointing out my error - the solution as written here worked for me as well.

Steve Langasek (vorlon) wrote :

Accepted into -proposed, please test and give feedback here

x7y7 (cmierda) wrote :

Solucion!! tienes que tener intalado virtualbox-os

sudo apt-get install virtualbox-ose-source
sudo m-a update
sudo m-a prepare
sudo m-a a-i virtualbox-ose
sudo /etc/init.d/vboxdrv restart

Un saludo

Would'n a dependency be a solution to this?

Letting virtualbox-ose-modules-generic or virtualbox-ose-modules-<version>-generic have a dependency to the corresponding version of linux-image-generic would hold back the kernel update until the corresponding virtualbox modules are also available, right?

Daniel Hahler (blueyed) wrote :

Please test the package from https://edge.launchpad.net/ubuntu/+source/virtualbox-ose-modules/24.0.3 - once it has been rebuild (or get it from the hardy-proposed repository) and provide feedback here, so that it can be copied to hardy-updates as soon as possible.

Changed in virtualbox-ose-modules:
status: In Progress → Fix Committed
rhi (rhi-deactivatedaccount) wrote :

Why are the vbox modules not available when there is a kernel update? I think it would be wise to compile & distribute all modules just with the kernel update

Daniel Hahler (blueyed) wrote :

> Would'n a dependency be a solution to this?
The module already depends on a kernel version, which causes already other problems (bug 226960)

> Why are the vbox modules not available when there is a kernel update?
It's not that easy. The packages are maintained independently (and virtualbox-ose(-modules) is only community-maintained, which currently means "by me").
See https://bugs.edge.launchpad.net/ubuntu/+source/virtualbox-ose/+bug/179807/comments/32 - it seems like we can get this fixed for Intrepid and hopefully also for Hardy.

> The module already depends on a kernel version, which causes already other problems (bug 226960)

The package "virtualbox-ose-modules-2.6.24-17-generic" depends on "linux-image-2.6.24-17-generic" but because the package "linux-image-2.6.24-17-generic" is retained when a kernel update is ditributed, the kernel gets updated and the dependencies are still met. So, for APT, all is well!

Making "virtualbox-ose-modules-2.6.24-17-generic" dependent on "linux-image-generic" with the exact version of 2.6.24-17 would hold back the kernel update until the correct virtualbox modules are available?

Making "virtualbox-ose-modules-generic" dependent on any "virtualbox-ose-modules-xxxxxx-generic" package (an OR statement), would always install the correct modules for the installed kernel, when "virtualbox-ose-modules-generic" is installed?

Only downside would be that people could be running a vulnerable kernel if the virtualbox modules are not updated fast enough... But for me personally, I wouldn't mind running a "vulnerable" kernel a day or two... Not being able to run virtualbox hampers me a lot more!

I think you can't force end users to a terminal each time they receive a kernel update... Hmm, difficult issue...

Mike (bild85) wrote :

Since a technical solution is likely not possible (as described above), just make the error message a little more practical. While the message provided is perfectly accurate, a clearer message might make users less jumpy when it 'breaks.' Something along the lines of:
if (kernel_modules_version < virtualbox-ose-modules_version) than
errormsg="kernel headers do not match virtualbox modules. Reboot and start with previous kernel or see the forums for the latest virtualbox modules"

Eric Buist (buisteric) wrote :

Same problem for me, and no working solution.
I have tried to module-assistant update, prepare and a-i stuff, without any success. Even though the virtualbox-source package is installed, the module does not compile.
I am using a x86_64 kernel. Can that have an influence?
For now, the only solution is to remove VirtualBox and use QEmu instead.

chastell (chastell) wrote :

Daniel Hahler: virtualbox-ose-modules-2.6.24-18-generic works for me. Thanks!

andrea (afa-iol) wrote :

Who knows when will be enable the new virtualbox module (virtualbox-ose-modules-2.6.24-18-generic)
in synaptic ?

Rony (berrold) wrote :

Can possible just to change the way I see in Linux about error messages? I mean because more regular users use Ubuntu Linux , error messages must be less technical (meaningless for humain now) but more usefull and practical?
Example , just this:\
If the maintainer see dependency problems all time. OK. Just change error message instead meaningless message about some package and all these stuff just Write :
//////////////////////////
This Package [Number] is depend on Current Kernel Number [N]. Now it is installed [Number of currentPackage].
You Must To Do Next to get the Package Working:

sudo apt-get install virtualbox-ose-source /
sudo module-assistant update /
sudo module-assistant prepare /
sudo module-assistant a-i virtualbox-ose /
sudo /etc/init.d/vboxdrv restart /

Any messages are logging into /var/log/VirtualBoxLog
/////////////////////////////////////

That's all, guys!

By such kind of message I mean human and parctical, Regular users won't be in panic and infinite calls WoW! What's going now? What I did ? and so on.
Thanks.

aTarom (atarom) wrote :

Thanks, this work perfectly (U8.04-i386)

sudo apt-get install virtualbox-ose-source
sudo module-assistant update
sudo module-assistant prepare
sudo module-assistant a-i virtualbox-ose
sudo /etc/init.d/vboxdrv restart

I like the Rony example

GG (giorgio-gilestro) wrote :

The proposed 2.6.24-18-generic worked ok for me. (8.04)
Thanks

T. Middleton (timtoo) wrote :

The module-assistant method did not work for me (on AMD64). Below is snip from the build log.

    │ {standard input}: Assembler messages: │
    │ {standard input}:437: Error: suffix or operands invalid for `pushf' │
    │ {standard input}:438: Error: suffix or operands invalid for `pop' │
    │ {standard input}:479: Error: suffix or operands invalid for `push' │
    │ {standard input}:480: Error: suffix or operands invalid for `popf' │
    │ {standard input}:4178: Error: suffix or operands invalid for `mov' │
    │ {standard input}:5251: Error: suffix or operands invalid for `mov' │
    │ kmk[4]: *** [/usr/src/modules/virtualbox-ose/SUPDRVShared.o] Error 1 │
    │ kmk[3]: *** [_module_/usr/src/modules/virtualbox-ose] Error 2 │
    │ kmk[3]: Leaving directory `/usr/src/linux-headers-2.6.24-18-generic' │
    │ kmk[2]: *** [vboxdrv] Error 2 │
    │ kmk[2]: Leaving directory `/usr/src/modules/virtualbox-ose'

Daniel Hahler (blueyed) wrote :

Please read previous comments!
There's an updated package in hardy-proposed, which needs verification/feedback (and using it does not require to fiddle with module-assistant).

We need to get it verified and copied to hardy-updates as soon as possible, since there's a -19 kernel now already in hardy-proposed and it would be nice, if the next kernel ABI would cause less trouble for virtualbox-ose-modules!

Confirmed the hardy-proposed modules. Working fine running Latest kernal on 64-bit ubuntu.

Guillermo Molleda (gmolleda) wrote :

Confirmed the hardy-proposed modules. Working fine running Latest
kernal on 32-bit ubuntu (intel pentium dual-core)

Ubuntu 8.04 Desktop AMD64 with all updates, including hardy-proposed. VirtualBox works fine running the 2.6.24-18 kernel and associated VirtualBox modules. I just uninstalled the old virtualbox-ose-modules-2.6.24-16 package, then installed the virtualbox-ose-modules-generic metapackage. No reboot required since I was already running the new kernel. Roll that bad boy out I say. ;)

andrea (afa-iol) wrote :

The proposed 2.6.24-18-generic worked ok also for me. (8.04)
Thanks

Daniel Hahler (blueyed) wrote :

Subscribing ubuntu-archive, hoping that it is appropriate.

Asermar (alexis-okodex) wrote :

The proposed 2.6.24-18-generic worked fine for me.
8.04 64bits

drkitty (cat-psychology) wrote :

x7y7 and Ronny have the solution. That worked perfectly. :-}

Chimo (chimo) wrote :

The proposed 2.6.24-18-generic worked fine for me as well.
Kubuntu 8.04 32bits

spandanj (spandanj) wrote :

after the kernel update to '-18', and still having VBox ose module that is '-17'. i did the following as suggested:

sudo apt-get install virtualbox-ose-source /
sudo module-assistant update /
sudo module-assistant prepare /
sudo module-assistant a-i virtualbox-ose /
sudo /etc/init.d/vboxdrv restart /

It works...BUT somehow the audio doesn't work...

SCRATCH that. It didn't work with the ALSA that i was using previously. after the 5 steps here i had the change the audio from ALSA to Pulse. does this mean anything? bad?

ALSO, once the "virtualbox-ose-modules-generic 2.6.24-18' is updated in the ubunty repositories, can i simply update it normally. ie. will these 5 steps that i conducted affect or even not allow me to update to the new version of module?

Proposed 2.6.24-18-generic works fine here (8.0.4_64).

I hope the update process can be improved in the future to avoid the extra step for the VirtualBox module. It's no biggie, but the first time I've ran into the issue, it was quite scary that a recommended update broke an important application. If there's anything I can do to help, please let me know. Thanks for all your efforts.

DenialP (danlezoche) wrote :

Proposed update worked for me.

Thanks,

Dan

The proposed update works on 8.04 x86_64, but I had to add the users to the vboxusers group manually. If that's the normal behavior, it's OK.

andrewg (andrew-reurbanise) wrote :

Thanks, Daniel, the update worked for me too.

FYI Linux kernel 2.6.24-19 just appeared in hardy-proposed, yet there is no corresponding VirtualBox module. Looks like this problem is going to persist in future kernel updates possibly. Perhaps they should be "linked," if only in the repository maintainers' minds, the same way the restricted modules (NVIDIA drivers, etc.) are linked.

Proposed update works for me too.

Martin Pitt (pitti) wrote :

Copied to hardy-updates. Please note that hardy-proposed has kernel -19 now, thus v-o-m needs another update.

Changed in virtualbox-ose-modules:
status: Fix Committed → Fix Released
Ahmet Öztürk (dmxe) wrote :

proposed update works like a charm. thanks a lot.

Daniel Hahler (blueyed) wrote :

Thanks for copying it, Martin.

I'll upload a new module for 2.6.24-19 in a minute, after testbuilding it (see bug 238019 for this).

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers