Bug 581747

Summary:	QEMU HD unreadable
Product:	[Fedora] Fedora	Reporter:	pleabargain <dennisgdaniels>
Component:	virt-manager	Assignee:	Cole Robinson <crobinso>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	12	CC:	berrange, crobinso, hbrock, jforbes, virt-maint
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-04-13 16:59:48 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description pleabargain 2010-04-13 07:17:55 UTC

Description of problem:
QEMU HD unreadable
Install on VM fails

Version-Release number of selected component (if applicable):


How reproducible:
everytime

Steps to Reproduce:
1.install elastix on VM
2.
3.
  
Actual results:
qemu drive unreadable

Expected results:


Additional info:
Video of bug
http://www.youtube.com/watch?v=NK5Ret0S1_s

Comment 1 pleabargain 2010-04-13 14:34:26 UTC

This is reproducible
QEMU HD unreadable.
version:
rpm -qa |grep virt
libvirt-python-0.7.1-15.fc12.i686
libvirt-0.7.1-15.fc12.i686
virt-viewer-0.2.0-1.fc12.i686
virt-manager-0.8.2-3.fc12.noarch
libvirt-client-0.7.1-15.fc12.i686
python-virtinst-0.500.1-2.fc12.noarch



Please see videos here
 http://www.youtube.com/watch?v=NK5Ret0S1_s
and here
 http://www.youtube.com/watch?v=Tkhf_hZHRWk
showing same behavior.

Comment 2 Cole Robinson 2010-04-13 16:59:48 UTC

That warning from anaconda basically means it cannot detect any partition table on your drive (the disk image virt-manager created) so the installer wants to initialize the drive. If you created new storage, it is safe to continue, since there is no data to lose.

*** This bug has been marked as a duplicate of bug 492082 ***

Comment 3 pleabargain 2010-04-14 08:47:19 UTC

Thanks for the pointer but I'm very confused as to why one ISO (Elastix) would say QEMU was unreadable and another (Trixbox) would plow along merrily (and then crash Fedora12 in mid install?)

Here is a vid of the difference in behaviors:
http://www.youtube.com/watch?v=qk_o7Ahxb2g

many thanks for your support,
Dennis