Jump to content

Virtual Box Issues with Latest Kernel Update


Mitchell
 Share

Recommended Posts

Hi people, just though I'd post this if anyone else has any problems. I've managed to solve it for myself, but nowhere near as smooth as the update from kernel 2.6.22.9.

 

Like most of you I found the latest kernel update to 2.6.22.12-desktop-1mdv from my updates tool yesterday, and tried it out this morning. This fixes some security issues, so I thought it was a good idea. The last update was flawless, this less so. The problem (so far) was with Virtual Box, which I'm using for a few business files which I have. Here are the packages I installed to get it working properly again. Some of them might not have been needed, I'm pretty sure it was the very last package which got it working again. Hope this helps anybody else who runs across this.

 

- dkms-vboxadd-1.5.0-6mdv2008.0.i586

- dkms-vboxvfs-1.5.0-6mdv2008.0.i586

- vboxadd-kernel-2.6.22.12-desktop-1mdv-1.5.0-6mdv2008.0.i586

- vboxvfs-kernel-2.6.22.12-desktop-1mdv-1.5.0-6mdv2008.0.i586

- kernel-desktop-devel-2.6.22.12-1mdv-1-1mdv2008.0.i586

- kernel-desktop-devel-latest-2.6.22.12-1mdv2008.0.i586

- virtualbox-kernel-2.6.22.12-desktop-1mdv-1.5.0-6mdv2008.0.i586

Link to comment
Share on other sites

These three are the only you actually needed:

 

vboxadd-kernel-2.6.22.12-desktop-1mdv-1.5.0-6mdv2008.0.i586

vboxvfs-kernel-2.6.22.12-desktop-1mdv-1.5.0-6mdv2008.0.i586

virtualbox-kernel-2.6.22.12-desktop-1mdv-1.5.0-6mdv2008.0.i586

 

there was, unfortunately, a process error which meant the kernel update was released without the external module packages (the Virtualbox modules, NVIDIA modules, ATI modules etc) being rebuilt and released at the same time, resulting in this situation. They have now been released and updated (as you can see from the existence of the above packages), but the -latest 'metapackages' (which ensure that MandrivaUpdate automatically installs these updates) still haven't been uploaded, for some reason; Vincent is sorting that out at present.

 

The correct process is for the kernel packages, module packages and -latest metapackages to all be built and released simultaneously - as you mentioned, this was done correctly for 2.6.22.9-2mdv, so that update went very smoothly. The kernel and security teams are currently working with each other to ensure that this problem never happens again, so all future kernel updates should go as smoothly as 2.6.22.9-2mdv did, and not bumpy like this one :(

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...