Bug 1273107 - virtualbox unable to start virtual machines after update to kernel 4.2.3-200
virtualbox unable to start virtual machines after update to kernel 4.2.3-200
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
22
Unspecified Unspecified
unspecified Severity medium
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-10-19 11:44 EDT by Ambrogio
Modified: 2015-10-20 08:59 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-10-20 08:59:41 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


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

  None (edit)
Description Ambrogio 2015-10-19 11:44:05 EDT
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 08:59:41 EDT
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.