Bug 1373424 - Kernel 4.7.201.FC24 (and Kernel 4.7.2.101.FC23) crash on boot in VirtualBox VM with Guest Additions
Summary: Kernel 4.7.201.FC24 (and Kernel 4.7.2.101.FC23) crash on boot in VirtualBox V...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 24
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-06 09:11 UTC by xavier268
Modified: 2016-09-06 11:17 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-06 11:17:07 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Video capture of crash during boot.(flash) (1.12 MB, application/x-shockwave-flash)
2016-09-06 09:11 UTC, xavier268
no flags Details

Description xavier268 2016-09-06 09:11:07 UTC
Created attachment 1198146 [details]
Video capture of crash during boot.(flash)

Description of problem:
Kernel panic during boot in a VBox VM when Guest Additions are installed.
Booting with kernel 4.6.xx works fine. Appears both in fed23 and fed24.
Booting without guest additions works, but screen is not useable.

Version-Release number of selected component (if applicable):
Kernel 4.7.2.101.F23 and Kernel 4.7.2.201.fed 24
Virtual Box VM 5.2.26 with Guest Additions (5.2.26)
Host is Windows10 i7 and 16G ram.

How reproducible:
Systematic

Steps to Reproduce:
Same issue with both fed 23 and fed 24.
Create a new VM from xfce-live-x64 fed 23 or 24
Install, boot, works.
dnf update (to 7.2.x01 )
reboot, ok.
Install guest additions.
reboot -> crash
reboot with 4.6.x -> ok
install gest additions on 4.6.x and reboot  -> ok

Actual results:

Crash during boot (see video)

Expected results:

Updating should not downgrade bootability

Additional info:

Comment 1 Josh Boyer 2016-09-06 11:17:07 UTC
Fedora doesn't provide or support out of tree kernel modules.  You will need to take this up with VMWare.


Note You need to log in before you can comment on or make changes to this bug.