Bug 22092 - virtualbox-kernel stuck at kernel version 4.13.12
Summary: virtualbox-kernel stuck at kernel version 4.13.12
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-11-28 19:59 CET by Hans Micheelsen
Modified: 2017-12-18 08:43 CET (History)
1 user (show)

See Also:
Source RPM: kmod-virtualbox-5.1.30-7.mga7.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Hans Micheelsen 2017-11-28 19:59:56 CET 
Description of problem:
The kernel has been updated to version 4.14.2 but it seems that virtualbox-kernel stays at 4.13.2

Version-Release number of selected component (if applicable):
virtualbox-kernel-4.13.12-desktop-2.mga7

How reproducible:


Steps to Reproduce:
1. Update with:  /bin/sudo urpmi --auto-select --auto-update
2.
3.
Comment 1 Marja Van Waes 2017-11-29 08:28:49 CET 
Thomas Backlund explained why on IRC some time ago:

2017:11:21:21:57< tmb> kernel is shaping up nicely... the only part missing is virtualbox proper support for 4.14 series kernels

CC: (none) => marja11
Assignee: bugsquad => tmb

Comment 2 Thomas Backlund 2017-11-29 09:13:51 CET 
Seems the prebuilt kmod builds failed...
If you want virtualbox support fast, install kernel-desktop-devel-latest and dkms-virtualbox

I will fix up the kmod builds tonight or tomorrow
Comment 3 Hans Micheelsen 2017-12-17 20:55:04 CET 
I think this one can be closed, Can't it?
Comment 4 Thomas Backlund 2017-12-18 08:43:22 CET 
yep

Resolution: (none) => FIXED
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.