Bug 1273107

Summary: virtualbox unable to start virtual machines after update to kernel 4.2.3-200
Product: [Fedora] Fedora Reporter: Ambrogio <ambrogio.de.lorenzo>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 22CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-10-20 12:59:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Logs for the VM start none

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.