Bug 733082

Summary: F16 alpha install in VirtualBox stuck at encrypting /home
Product: [Fedora] Fedora Reporter: Marius Andreiana <marius.andreiana>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED CANTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: anaconda-maint-list, jonathan, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-09-05 19:15:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
/tmp/anaconda.log
none
/tmp/program.log
none
/tmp/storage.log
none
/var/log/messages none

Description Marius Andreiana 2011-08-24 16:53:40 UTC 
How reproducible:
100%

Steps to Reproduce:
1. Install VirtualBox 4.1.2 (on OSX in my case)
2. Create a virtual machine, 30gb expandable .vdi HDD
3. install fedora. Custom partition: /, swap, /home (encrypted ext4)
 
Actual results:
stuck at encrypting /home (more than 1h, tried twice). CPU is used 100% by VirtualBox
Comment 1 David Lehman 2011-08-24 17:03:02 UTC 
Please attach the following log files individually to this bug report:

 /tmp/anaconda.log
 /tmp/program.log
 /tmp/storage.log
 /tmp/syslog
Comment 2 Marius Andreiana 2011-08-24 17:59:55 UTC 
Created attachment 519681 [details]
/tmp/anaconda.log
Comment 3 Marius Andreiana 2011-08-24 18:00:56 UTC 
Created attachment 519682 [details]
/tmp/program.log
Comment 4 Marius Andreiana 2011-08-24 18:02:11 UTC 
Created attachment 519683 [details]
/tmp/storage.log
Comment 5 Marius Andreiana 2011-08-24 18:05:46 UTC 
Created attachment 519684 [details]
/var/log/messages
Comment 6 Marius Andreiana 2011-08-24 18:06:08 UTC 
There is no /tmp/syslog
Comment 7 Chris Lumens 2011-09-05 19:15:40 UTC 
This sounds like a bug in the handling of devices by VirtualBox, which we can't do anything about.  I can't reproduce on regular hardware or with kvm.