Please update virtualbox-modules for 2.6.24-21 (copy to updates together with kernel)

virtualbox-ose-modules-2.6.24-20 is the latest package but 2.6.24-21 is available in hardy-proposed

accepted into hardy-proposed, please test.

This has happened quite a lot in the past. I wonder why Ubuntu can not avoid creating the same predicament after it happened more than twice?

i was having issues with vmware on vista but i got a copy of vmware
workstation and everything is ok

On Sat, Aug 30, 2008 at 10:49 PM, Lothar <email address hidden> wrote:

> This has happened quite a lot in the past. I wonder why Ubuntu can not
> avoid creating the same predicament after it happened more than twice?
>
> --
> has not been built for kernel 2.6.24-21
> https://bugs.launchpad.net/bugs/260722
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Jonathan Aquilina

It doesn't seem to have entered hardy-proposed yet, even though LP reports it as successfully built.
https://launchpad.net/ubuntu/hardy/+source/virtualbox-ose-modules/24.0.6

Is there any special reason for that?

Agreed. I don't see it in hardy-proposed either.

I'm checking 2 mirrors and us.archive.ubuntu.com

It is waiting in the NEW queue:
https://edge.launchpad.net/ubuntu/hardy/+queue?queue_state=0&queue_text=virtualbox

I've tried the:
"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"
but I'm getting:
" * Stopping VirtualBox kernel module vboxdrv [ OK ]
 * Starting VirtualBox kernel module vboxdrv
 * No suitable module for running kernel found."

Same for me but an error is appearing at the 3rd step of 'sudo m-a a-i virtualbox-ose' and seems to come from /usr/src/modules/virtualbox-ose/SUPDRVShared.c.
A lot of warnings are also mentioned concerning ' «cdecl» attribute ignored '.
See the attached file.

If I continue to the next step, I'm getting the same message than you (logic as the error is stopping the process)
   " * Stopping VirtualBox kernel module vboxdrv [ OK ]
     * Starting VirtualBox kernel module vboxdrv
     * No suitable module for running kernel found."

I am on AMD64 seen as x86_64, kernel 2.6.24-21-generic

There's a systemic problem here with Ubuntu, not just one not-updated module.

(a) this bug happens *every* minor kernel update;
(b) the module apparently exists, but has been held back for *weeks* with no decent explanation
(c) leaving all VirtualBox VMs unusable on what's supposed to be the stable version of Ubuntu. Where stuff doesn't just suddenly break and stay broken for weeks.

Making bugs into duplicates of duplicates of duplicates doesn't get the VMs running.

Is there anyone who (a) gives a hoot and (b) can resolve whatever systemic problem makes this keep reoccuring, who could please have it brought to their attention?

Binary packages accepted into hardy-proposed, please test.

Binary package tested and seems ok for me (64 bits version).
Thanks.

Packages tested and seems okay for me too; i386 version.

yes, it works nice to.. i386

2008/9/9 Andreas Wenning <email address hidden>

> Packages tested and seems okay for me too; i386 version.
>
> --
> has not been built for kernel 2.6.24-21
> https://bugs.launchpad.net/bugs/260722
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--
Ali Deniz EREN
<email address hidden>

Marking verification-done.

Please, don't copy it to hardy-updates, before the kernel is there (and not much later).

Copied to hardy-updates along with the -21 kernel.

this is affecting qemu as well. I do OS development and am halted due to this. OSX is also affected by this.

will try to update my cross linker tools for OSX, but if I cant emu test stuff that triple faults without taking down the OS(host) I CANNOT solve the problem within mine so it doesn't triple fault.

Drivers seems to be affected by this as well. My usb audio (ps2 headset) got knocked off and wouldnt come back due to 'forced' updates for the kernel. True users have an option of not upgrading, but who wants to leave a security hole wide open?

I agree on the debian is more stable, but for some reason, I keep getting enviroments like 486-linux instead of 686-linux and cant build anything from scratch.(and I have the dev tools installed properly). I have limited bandiwdth (5GB) I cant DL the debian repos every time i need a stable OS.

Im using both a mini(ubuntu 8.10) and a PC(OSX). The Core CPU in my mini HAS the intel vm mode ability, the Dual core PC does not.

This is a non-issue today as all the kernel-modules are automatically fixed when you get a new kernel.
I suggest that you update to a newer release. In at least the last two releases(9.04 and 9.10), this has not been a problem.

Pascal, Hardy is still a LTS and therefore it should/must get fixed.
I'll look into this later today.

@darkraven: you should have filed a new bug instead really.

Ok, sorry for misunderstanding this: virtualbox-ose-modules is OK for Hardy (the last kernel security update is 8 weeks old already).

And Pascal is right, it's a non-issue with later releases already.

You can work around this by installing "module-assistant" and running it to re-compile modules for vbox and kqemu
against the newer kernel.

I have been doing this now for years with success, and it is quite straightforward, except that the interface for m-a is not quite 'intuitive' ;)

Same problem with ubuntu 8.04.4 LTS, kernels available 2.6.24-28-generic and later, but only virtualbox-ose-modules-2.6.24-27-generic modules available.

Thanks for notifying me, I've created bug 615516 about this.