Description of problem: virt-inst asks to Re-Initialize sda drive while creating a VM(despite creating a _new_ vm image) "Error processing drive sda Maybe it needs to be reinitialized. YOU WILL LOSE ALL DATA ON THIS DRIVE" I can also confirm that the disk image is a _new_ one ( and _not_ an existing disk image which has old data from a previous guest) =============================================================== domname=testbox location=http://10.65.x.x/fedora/linux/releases/11/Fedora/x86_64/os/ vmimage="/export/libvirtimages/$domname.img" echo "Creating domain $domname" echo "Image is here $vmimage" echo "Location of the OS sources $location" virt-install --connect=qemu:///system \ --network=bridge:br0 \ --extra-args="ks=http://10.65.y.y/ks-with-brtfs.ks console=tty0 console=ttyS0,9600" \ --name $domname \ --file=$vmimage \ --file-size=8 \ --ram 1024 \ --accelerate \ --nonsparse \ --location=$location \ ============================================================= Note: here also tried with --force (which says "yes" for all prompts) with virt-install. does not improve the result Version-Release number of selected component (if applicable): python-virtinst: 0.400.3 host: F11(x64) guest: F11(x64) How reproducible: Always Steps to Reproduce: 1. use virt-install as in description. After picking the image(and a few details from kickstart, it asks to Re-initialize the drive. (though this proceeds if we /do/ click on Re-initialize the drive) Actual results: A warning is thrown : "Error processing drive sda Maybe it needs to be reinitialized. YOU WILL LOSE ALL DATA ON THIS DRIVE" Expected results: No warning should be thrown. (or atleast virt-inst _should_ proceed silently when --force is used. I have not tried with the latest python-virtinst(0.500.0) from rahwide as I currently don't have an installed "host" with rawhide/f12beta. any clue on what I'm missing here?
Kickstart I used.. ======================================= install text lang en_US.UTF-8 keyboard us rootpw somepassword firewall --service=ssh authconfig --enableshadow --passalgo=sha512 selinux --enforcing timezone --utc Asia/Kolkata bootloader --location=mbr --append="rhgb console=tty0 console=ttyS0,9600" icantbelieveitsnotbtr clearpart --linux part /boot --fstype ext3 --size=100 part / --fstype ext3 --size=1500 part /export --fstype btrfs --size=2000 %packages @core @editors @text-internet %end %post ====================================== And I haven't seen any info from the logs (/var/log/libvirt/qemu/testbox.log)
Yes, this is a known issue. I'm actually going to close this as a dup of BZ 492082, which has gone on for quite some time. Chris Lalancette *** This bug has been marked as a duplicate of bug 492082 ***