Bug 1273107 - virtualbox unable to start virtual machines after update to kernel 4.2.3-200
Summary: virtualbox unable to start virtual machines after update to kernel 4.2.3-200
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-19 15:44 UTC by Ambrogio
Modified: 2015-10-20 12:59 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-20 12:59:41 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
Logs for the VM start (239.52 KB, text/plain)
2015-10-19 15:44 UTC, Ambrogio 		no flags Details
View All

Description Ambrogio 2015-10-19 15:44:05 UTC 
Created attachment 1084448 [details]
Logs for the VM start

Description of problem:

Virtual Machines unable to start after kernel update.

Version-Release number of selected component (if applicable):
 Kernel Installed kernel-4.2.3-200.fc22.x86_64.rpm
 VirtualBox-4.3-4.3.30_101610_fedora22-1.x86_64.rpm

How reproducible:
Simply start a virtual machines

Steps to Reproduce:
1. Boot with new kernel
2. Start VirtualBox
3. Start a Virtual Machines

Actual results:
 Guru Meditation

Expected results:
 Normal Boot

Additional info:
 No issues booting with kernel-4.1.10-200.fc22.x86_64.rpm
 No VirtualBox updates
Comment 1 Josh Boyer 2015-10-20 12:59:41 UTC 
Fedora does not provide or support third party kernel modules or Virtualbox.  You will need to contact whomever you got it from.
Note You need to log in before you can comment on or make changes to this bug.