Bug 20086 - Mageia in Virtualbox VM failed to launch X since kernel 4.4.32 (4.4.36 & 4.4.39)
Summary: Mageia in Virtualbox VM failed to launch X since kernel 4.4.32 (4.4.36 & 4.4.39)
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-08 12:12 CET by rexy
Modified: 2018-09-18 15:35 CEST (History)
3 users (show)

See Also:
Source RPM: virtualbox-kernel-server-latest
CVE:
Status comment:

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

Description rexy 2017-01-08 12:12:53 CET 
Since the update of the kernel 4.4.32 (4.4.32, 4.4.36 & 4.4.39), Virtualbox Mageia VM failed to launch X. These Mageia VM work fine when booting with previous kernel (4.4.30)

Error reporting in "/var/log/Xorg.0.log" :
(II) VboxVideo : guest driver for VirtalBox: vbox
(II) vboxvideo : kernel driver found, not loading
(EE) No devices detected.
(EE) no screens found

RPM installed in the VM :
virtualbox-guest-additions-5.1.10-1.1.mga5
x11-driver-video-vboxvideo-5.1.10-1.1.mga5
kernel-desktop-4.4.39-1.mga5-1-1.mga5
vboxadditions-kernel-4.4.39-desktop-1.mga5-5.1.10-3.1.mga5

kernel-desktop-4.4.30-2.mga5-1-1.mga5
vboxadditions-kernel-4.4.30-desktop-2.mga5-5.1.2-10.mga5

Reproductible : install mga5.1 in a VM and update the kernel of this VM
Comment 1 Marja Van Waes 2017-01-08 17:25:33 CET 
@ tmb,

I can't think of any smart questions to ask the reporter, so I'll leave that to you :-)

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

Comment 2 rexy 2017-02-28 23:41:34 CET 
The problem is the same with the new kernel 4.4.50.
All is fine, when booting with the 4.4.30
Comment 3 rexy 2017-03-01 00:10:10 CET 
Comparing the two Xorg.0.log, i see that 

- kernel 4.4.30 (X11 working)
 X.Org Server Extension : 8.0
 (EE) systemd-logind: failed to get session: PID 886 does not belong to any known session
 (--) PCI:*(0:0:2:0) 80ee:beef:0000:0000 rev 0, Mem @ 0xe0000000/16777216
...

- kernel > 4.4.30 (X11 not working)
  X.Org Server Extension : 8.0
  (II) systemd-logind: took control of session /org/freedesktop/login1/session/c1
  (II) xfree86: Adding drm device (/dev/dri/card0)
  (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 10 paused 0
  (--) PCI:*(0:0:2:0) 80ee:beef:0000:0000 rev 0, Mem @ 0xe0000000/16777216
...
Comment 4 Michael Steen 2017-04-27 03:00:41 CEST 
Still a problem with kernel 4.4.59 and virtualbox 5.1.18.
Boots fine with kernel 4.4.30 and vbox 5.1.2.

CC: (none) => linux

Comment 5 rexy 2017-05-15 23:51:29 CEST 
Still a problem with kernel 4.4.65 and virtualbox 5.1.22
Boots fine with kernel 4.4.30 and vbox 5.1.22
Comment 6 Marja Van Waes 2018-09-18 15:35:06 CEST 
Hi rexy,

Thank you for having taken the needed time to report this issue!

We regret if this issue didn't get fixed in Mageia 5.

Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It continued to get limited extended support since then, but that support has now ended, too.

I assume this bug doesn't exist in Mageia 6 or later, because the kernel and virtualbox are much newer there.

Closing as OLD.

Please reopen this report and change its "Version:" at the top left to "6", if the same bug still exists in Mageia 6.

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