Bug 807401 - xen kernel crashes when using encrypted filesystem
Summary: xen kernel crashes when using encrypted filesystem
Status: CLOSED DUPLICATE of bug 804347
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel-xen
Version: 16
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Xen Maintainance List
QA Contact: Virtualization Bugs
Depends On:
TreeView+ depends on / blocked
Reported: 2012-03-27 17:06 UTC by Gerry Reno
Modified: 2012-03-31 20:19 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2012-03-27 18:18:26 UTC
Type: ---

Attachments (Terms of Use)

Description Gerry Reno 2012-03-27 17:06:13 UTC
Description of problem:
I installed F16 on an encrypted filesystem.  Baremetal kernel boots fine (3.2.10 and 3.3.0).  However, when I try to boot any of the Xen entries (4.1, 4.1.2) the kernel panics immediately on start of boot.  No prompt is given to enter encrypted filesystem password.  

Version-Release number of selected component (if applicable):
kernel 3.2.10
kernel 3.3.0

How reproducible:

Steps to Reproduce:
1. install F16 on encrypted filesystem
2. install Xen
3. try to boot any Xen boot entry
Actual results:
kernel panics

Expected results:
receive prompt for encrypted filesystem password and system then boots Xen kernel.

Additional info:

Comment 1 Konrad Rzeszutek Wilk 2012-03-27 17:54:02 UTC
Is this a dup of 804347 ?

Comment 2 Gerry Reno 2012-03-27 18:02:32 UTC
Konrad, That bug seems related to APIC.

When I boot both 3.2.10 and 3.3.0 without Xen they boot fine so I don't think this bug is the same problem.


Comment 3 Gerry Reno 2012-03-27 18:18:26 UTC
Konrad, I just looked again at the kernel panic screen and it is nearly the same as the one in bug 804347 so this may indeed be the same issue.

Marking as dup of 804347.

*** This bug has been marked as a duplicate of bug 804347 ***

Comment 4 Gerry Reno 2012-03-31 20:19:00 UTC
I tested with kernal-PAE-3.3.0-8 and the kernel panic is now gone but all is still not well with xen kernel bootup.  I'll open another bug on what I see now.

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