Bug 23883 - Virtual machine cannot run with server kernel
Summary: Virtual machine cannot run with server kernel
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-22 11:19 CET by Pierre Jarillon
Modified: 2018-11-22 23:50 CET (History)
1 user (show)

See Also:
Source RPM: kernel-server-latest-4.18.12-1.mga6
CVE:
Status comment:

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

Description Pierre Jarillon 2018-11-22 11:19:00 CET 
kernel-server-latest-4.18.12-1.mga6 and virtualbox-5.2.22-1.mga6 cannot work together.

A virtual machine Windows 7 was running perfectly until virtualbox was numbered 5.2.20 or 5.2.22. Now, a request for vboxdrv is made and the virtual machine cannot start.

After a long search, I have started the physical machine with a desktop kernel kernel-desktop-latest-4.14.78-1.mga6 allowing to start Windows 7.

This is tested with 5 physical machines.
Comment 1 Thomas Backlund 2018-11-22 13:33:40 CET 
Backport kernels dont have prebuilt kmods, so you need to install dkms-virtualbox and kernel-server-devel-latest to use virtualbox with it

Status: NEW => RESOLVED
CC: (none) => tmb
Resolution: (none) => INVALID

Comment 2 Pierre Jarillon 2018-11-22 18:33:51 CET 
I understand but:

1- I have tried to load kernel-server-devel-latest - this is not enough because vboxdrv is not compiled when it is loaded

2- No clear message is provided... I have found after reading a bunch of files.

3- This is a regression for Mageia, it was working before the updates.

I don't know if this is related to the kernel, virtualbox, the package or anything else...
A search in the about vboxdrv tells in the best case to run 
'/etc/init.d/vboxdrv setup' but it does not exists in Mageia.
I understand that you don't want to solve the problem. At least a clear message and and a little  documentation must be provided.

Resolution: INVALID => (none)
Status: RESOLVED => REOPENED

Comment 3 Thomas Backlund 2018-11-22 18:38:14 CET 
(In reply to Pierre Jarillon from comment #2)
> I understand but:
> 
> 1- I have tried to load kernel-server-devel-latest - this is not enough
> because vboxdrv is not compiled when it is loaded


Because you dont have dkms-virtualbox installed.


> 3- This is a regression for Mageia, it was working before the updates.


Backports IS NOT UPDATES !

If you cant handle backports, dont use them

Status: REOPENED => RESOLVED
Resolution: (none) => INVALID

Comment 4 Pierre Jarillon 2018-11-22 18:51:13 CET 
I disagree, I have never use backports!

kernel-server-4.14.78-1.mga6 - Linux Kernel for server use with x86_64​                                                                                                                         
Attention : C'est une mise à jour officielle qui est supportée par Mageia.

  Média : Core Updates (distrib3)

Resolution: INVALID => (none)
Status: RESOLVED => REOPENED

Comment 5 Thomas Backlund 2018-11-22 18:56:02 CET 
Sigh,

read you own initial report:

"kernel-server-latest-4.18.12-1.mga6 and virtualbox-5.2.22-1.mga6 cannot work together"

That kernel is in backports !

Status: REOPENED => RESOLVED
Resolution: (none) => INVALID

Comment 6 Pierre Jarillon 2018-11-22 23:50:23 CET 
I don't how it come: only core, non-free and tainted and their updates are selected...

Resolution: INVALID => FIXED
Note You need to log in before you can comment on or make changes to this bug.