Bug 718690

Summary: Can't unlock encrypted Physical Volume with kernel-xen on KVM guest
Product: Red Hat Enterprise Linux 5 Reporter: Alexander Todorov <atodorov>
Component: kernel-xenAssignee: Xen Maintainance List <xen-maint>
Status: CLOSED NOTABUG QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 5.6CC: drjones, leiwang, lersek, pcao, qwan, xen-maint
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-07-04 11:36:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 693654    

Description Alexander Todorov 2011-07-04 10:01:37 UTC 
Description of problem:

I'm hitting a strange issue where I can't unlock encrypted partitions after boot with kernel-xen. See steps to reproduce for more info.


Version-Release number of selected component (if applicable):
kernel-xen-2.6.18-272.el5
cryptsetup-luks-1.0.3-8.el5

How reproducible:
always

Steps to Reproduce:
1. Prepare a 6.1 KVM host
2. Create a domU selecting Linux/RHEL5.4+ for the OS type. 
3. Boot from RHEL 5.7 DVD
4. At the partitioning screen select "Encrypt system" and provide the pass phrase
5. At the package install screen I selected both the KVM and Xen virtualization groups (need proper key to enable them) - package selection was part of another test case.
6. Complete the install and reboot.
  
Actual results:
Both kernel and kernel-xen are installed. When booting with kernel-xen I get the message: 

Red Hat nash version 5.1.19.6 starting
insmod: error inserting '/lib/aes_generic.ko': -1 File exists
Loading /lib/kbd/keymaps/i386/qwerty/us.map
Enter LUKS passphrase for /dev/vda2:


I enter the correct pass phrase but it is not recognized.

Expected results:


Additional info:
When booting the same guest with the regular kernel and providing the same pass phrase it is recognized, luks partition is unlocked and system boots fine.
Comment 1 Alexander Todorov 2011-07-04 10:03:44 UTC 
FYI I get the same error text about aes_generic.ko when booting with the regular kernel but my pass phrase is recognized and I had no issues.
Comment 3 Andrew Jones 2011-07-04 11:36:13 UTC 
Running kernel-xen on top of a KVM host makes no sense.