Bug 1154139 - Kernel Panic on Host when running Fedora inside VM
Summary: Kernel Panic on Host when running Fedora inside VM
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: LiveCD
Version: 20
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-17 16:09 UTC by marius
Modified: 2015-06-29 22:57 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 22:57:16 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Photo taken with my smartphone of the panic log (1.68 MB, image/jpeg)
2014-10-17 16:09 UTC, marius
no flags Details

Description marius 2014-10-17 16:09:42 UTC
Created attachment 947969 [details]
Photo taken with my smartphone of the panic log

Description of problem:
Host: Arch linux with stock kernel
Hypervisor: VirtualBox 
When running Fedora inside VirtualBox and selecting install a kernel panic occurs on the host (=arch).

Version-Release number of selected component (if applicable):
Fedora LiveCD Desktop 20-1 x86_64

How reproducible:


Steps to Reproduce:
1. Start Fedora VM
2. Select install
(3. Choose English as language
 4. Choose German keyboard layout
 5. Remove English layout)
6. Begin installation
 

Actual results:
Kernel panic on host

Expected results:
Running Fedora installation in VM

Additional info:
Kernel version: 3.16.4-1-ARCH
VirtualBox version: 4.3.18-1
Preallocated virtual disk with 8GB
2048MB RAM
1 CPU Core
64MB Video RAM

Attached you'll find a photo taken with my smartphone of the panic log. I don't have kdump or something like that installed and I don't know any other way to provide a log, sorry. If you'll need a complete log I'll try to install kdump.

Comment 1 Fedora End Of Life 2015-05-29 13:06:47 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2015-06-29 22:57:16 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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