Bug 491132 - installation of guest fails with encryption
Summary: installation of guest fails with encryption
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-19 15:04 UTC by Dominick Grift
Modified: 2009-03-25 12:08 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-03-25 12:08:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Dominick Grift 2009-03-19 15:04:08 UTC
Description of problem:

When i try to install a guest to a encrypted partition or when i try to install a guest and have its partitions encrypted, the installation hangs.

I also tried without encryption and that works.

I am using an external usb disk.

Version-Release number of selected component (if applicable):
qemu.x86_64                2:0.10-0.9.kvm20090310git.fc11

How reproducible:
install a kvm/x86_64 fedora 11 guest on a logical volume on a luks encrypted pv.
installation hangs.

also occurs when you install using encrypted partitions in the guest only

if installed without using encryption at all it finishes the installation. (except that it hangs when it installs the boot loader but that is unrelated)

Comment 1 Mark McLoughlin 2009-03-25 11:05:21 UTC
If installing to encrypted partitions within the guest doesn't work, that sounds like an anaconda bug ... moving there.

Can you boot the guest with e.g. "console=ttS0 vnc" on the kernel command line and copy ~/anaconda.log from the guest?

Also, if you could try installing the guest with today's rawhide that would be helpful. There has been a lot of fixes going into anaconda's storage code in the past week

Comment 2 Dominick Grift 2009-03-25 12:08:27 UTC
To be honest i doubt this is the case: issue also occurs when installing to an enrypted partition (not within the installation).

Im closing this for now and will report again if and when i can give more details.


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