Advisory added as
type: bugfix
subject: Updated virtualbox packages fix various bugs
src:
  5:
   core:
     - virtualbox-5.0.16-1.mga5
     - kmod-vboxadditions-5.0.16-2.mga5
     - kmod-virtualbox-5.0.16-2.mga5
description: |
  Maintenance release updates virtualbox to version 5.0.16
references:
 - https://bugs.mageia.org/show_bug.cgi?id=18029
 - https://www.virtualbox.org/wiki/Changelog

Validating the update.

Keywords: (none) => validated_update
Whiteboard: (none) => MGA5-64-OK advisory
CC: (none) => davidwhodgins, sysadmin-bugs

Reverting validation, I forgot to mention it need to go out the same time as kernel-4.4.6

Keywords: validated_update => (none)
Depends on: (none) => 18031

Now that the Depends are there, it can be validated, as it won't be pushed until the kernel is ready to go.  I'll validate it once I test it again at home (hopefully tomorrow) if nobody beats me to it, but really it's good to go.

Whiteboard: MGA5-64-OK advisory => MGA5-32-OK MGA5-64-OK advisory

Testing on mga5-64

Packages installed cleanly

Extension pack (USB2 etc) updated without problems

In a winxp VM additions updated without problems

Everything working as it should

OK for mga5-64

Tested on Mageia 5 - 32-bit. 

Also tested kernel update in a Mageia 5 guest.

No problems noted.

CC: (none) => andrewsfarm

Removing OK's as this will be rebuilt against existing kernel and need retesting. 
Advisory will also need updating.

Adding feedback marker for now

Whiteboard: MGA5-32-OK MGA5-64-OK advisory => advisory feedback

Pushing this one separately from kernel 4.4.6 with kmods build for kernel-4.1.15-2.mga5, so:

SRPMS:
kmod-vboxadditions-5.0.16-3.mga5.src.rpm
kmod-virtualbox-5.0.16-3.mga5.src.rpm
virtualbox-5.0.16-1.mga5.src.rpm


i586:
dkms-vboxadditions-5.0.16-1.mga5.noarch.rpm
dkms-virtualbox-5.0.16-1.mga5.noarch.rpm
python-virtualbox-5.0.16-1.mga5.i586.rpm
vboxadditions-kernel-4.1.15-desktop-2.mga5-5.0.16-3.mga5.i586.rpm
vboxadditions-kernel-4.1.15-desktop586-2.mga5-5.0.16-3.mga5.i586.rpm
vboxadditions-kernel-4.1.15-server-2.mga5-5.0.16-3.mga5.i586.rpm
vboxadditions-kernel-desktop586-latest-5.0.16-3.mga5.i586.rpm
vboxadditions-kernel-desktop-latest-5.0.16-3.mga5.i586.rpm
vboxadditions-kernel-server-latest-5.0.16-3.mga5.i586.rpm
virtualbox-5.0.16-1.mga5.i586.rpm
virtualbox-devel-5.0.16-1.mga5.i586.rpm
virtualbox-guest-additions-5.0.16-1.mga5.i586.rpm
virtualbox-kernel-4.1.15-desktop-2.mga5-5.0.16-3.mga5.i586.rpm
virtualbox-kernel-4.1.15-desktop586-2.mga5-5.0.16-3.mga5.i586.rpm
virtualbox-kernel-4.1.15-server-2.mga5-5.0.16-3.mga5.i586.rpm
virtualbox-kernel-desktop586-latest-5.0.16-3.mga5.i586.rpm
virtualbox-kernel-desktop-latest-5.0.16-3.mga5.i586.rpm
virtualbox-kernel-server-latest-5.0.16-3.mga5.i586.rpm
x11-driver-video-vboxvideo-5.0.16-1.mga5.i586.rpm


x86_64:
dkms-vboxadditions-5.0.16-1.mga5.noarch.rpm
dkms-virtualbox-5.0.16-1.mga5.noarch.rpm
python-virtualbox-5.0.16-1.mga5.x86_64.rpm
vboxadditions-kernel-4.1.15-desktop-2.mga5-5.0.16-3.mga5.x86_64.rpm
vboxadditions-kernel-4.1.15-server-2.mga5-5.0.16-3.mga5.x86_64.rpm
vboxadditions-kernel-desktop-latest-5.0.16-3.mga5.x86_64.rpm
vboxadditions-kernel-server-latest-5.0.16-3.mga5.x86_64.rpm
virtualbox-5.0.16-1.mga5.x86_64.rpm
virtualbox-devel-5.0.16-1.mga5.x86_64.rpm
virtualbox-guest-additions-5.0.16-1.mga5.x86_64.rpm
virtualbox-kernel-4.1.15-desktop-2.mga5-5.0.16-3.mga5.x86_64.rpm
virtualbox-kernel-4.1.15-server-2.mga5-5.0.16-3.mga5.x86_64.rpm
virtualbox-kernel-desktop-latest-5.0.16-3.mga5.x86_64.rpm
virtualbox-kernel-server-latest-5.0.16-3.mga5.x86_64.rpm
x11-driver-video-vboxvideo-5.0.16-1.mga5.x86_64.rpm

Depends on: 18031 => (none)
Whiteboard: advisory feedback => advisory

Installed appropriate packages in a 64-bit MGA5 host (server kernel), then rebooted.
Ran Vbox, used the "Check for Updates" option to install new extpak.
Ran 64-bit Mageia 5 guest, installed appropriate packages, rebooted. All appeared OK.
Ran 32-bit Mageia 5 guest, installed appropriate packages, rebooted. All appeared OK.
Ran 32-bit Windows XP guest. More troublesome to update, but that's typical.

Not sure how to put this in the whiteboard, but I show 64-MGA5-host-OK, 64-MGA5-guest-OK, and 32-MGA5-guest-OK.

My 32-bit install capable of using VirtualBox still has the 4.4.6 kernel (working, AFAIK) and the 32-bit 5.0.16 virtualbox packages from that first upgrade attempt. (Also working, AFAIK) What do I need to do to do a proper 32-bit test of this one?

Ensuring it works when booting the 4.1.15-desktop-2 kernel should be sufficient.

(In reply to Dave Hodgins from comment #10)
> Ensuring it works when booting the 4.1.15-desktop-2 kernel should be
> sufficient.

Booting into the 4.1.15-2 i586 server kernel proceeded normally. VirtualBox 5.0.16 runs fine, as did the Mageia 5 guest.

Validating. Advisory was updated by Thomas.

Keywords: (none) => validated_update

An update for this issue has been pushed to the Mageia Updates repository.

http://advisories.mageia.org/MGAA-2016-0060.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED

CVE-2015-3197 also fixed in this update:
http://www.oracle.com/technetwork/security-advisory/cpuapr2016v3-2985753.html