Bug 484722 - Anaconda fails at partitioning step when running inside a kvm vm/qcow.
Summary: Anaconda fails at partitioning step when running inside a kvm vm/qcow.
Keywords:
Status: CLOSED DUPLICATE of bug 476433
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-02-09 16:53 UTC by Fabian Deutsch
Modified: 2009-02-11 15:04 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-02-11 15:04:57 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
Stacktrace (15.22 KB, text/plain)
2009-02-09 17:18 UTC, Fabian Deutsch 		no flags Details
View All

Description Fabian Deutsch 2009-02-09 16:53:31 UTC 
Description of problem:
Anaconda crashes with some stacktrace (attached) when trying to install it within a kvm/qcow2 vm.

Version-Release number of selected component (if applicable):
F10 host using kvm-83-3.fc11/2.6.29-0.48-rc2.git1.fc11.i686.
VM started with the commandline given in #484721

How reproducible:
Every time.

Steps to Reproduce:
1. Start vm
2. RUn Install to Hard Drive
3. Run trough the steps with some defaults
  
Actual results:
 Stacktrace after selecting use entire drive and pressing next

Expected results:
Drive gets partitioned.

Additional info:
Comment 1 Fabian Deutsch 2009-02-09 16:54:33 UTC 
disk image:
qemu-img create -f qcow2 f11.sys.qcow2 20G


commandline:
sudo qemu-kvm -cdrom Fedora-11-Alpha-i686-Live/F11-Alpha-i686-Live.iso -m
1024 -usb -hda f11.sys.qcow2 -vga std  -net user -net nic -smp 2
Comment 2 Fabian Deutsch 2009-02-09 17:10:47 UTC 
No change when using without smp.
Comment 3 Fabian Deutsch 2009-02-09 17:18:23 UTC 
Created attachment 331335 [details]
Stacktrace
Comment 4 Chris Lumens 2009-02-11 15:04:57 UTC 

*** This bug has been marked as a duplicate of bug 476433 ***
Note You need to log in before you can comment on or make changes to this bug.