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' ;)
--
Pleas
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.
--
Please update virtualbox-modules for 2.6.24-21 (copy to updates together with
kernel)
https
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.
--
Please update virtualbox-modules for 2.6.24-21 (copy to updates together with
kernel)
https://bugs.launchpad.net/bugs/260722
You r
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.
--
Please update virtualbox-modules for 2.6.24-21 (copy to updates
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 tripl
