Bug 757879

Summary:	virt-manager should hint wich disk format is better for the guest being created based on the information it already has
Product:	[Fedora] Fedora	Reporter:	Reartes Guillermo <rtguille>
Component:	virt-manager	Assignee:	Cole Robinson <crobinso>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	15	CC:	berrange, crobinso, dougsland, dpierce, hbrock, jforbes, virt-maint
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-01-18 15:53:11 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Reartes Guillermo 2011-11-28 21:23:07 UTC

Description of problem:

When creating a guest, one selects an os. So we give 
information to virt-manager of what we intend to run. So virt-manager should
just 'hint' wich disk format is better for the guest we are creating. 
In form of a short description "recommended" in the format combo list. 

For example "qcow    recommended" (with recommended in green).

If there is a known problem, the opposite may happend. a 
"non-recommended" in red.

Version-Release number of selected component (if applicable):
libvirt.x86_64              0.8.8-7.fc15           @updates
libvirt-client.x86_64       0.8.8-7.fc15           @updates
libvirt-python.x86_64       0.8.8-7.fc15           @updates
virt-manager.noarch         0.8.7-6.fc15           @updates
virt-viewer.x86_64          0.3.1-1.fc15           @fedora

How reproducible:
allways

Steps to Reproduce:
1. raw is allways selected by default.
  
Actual results:
raw everywhere 

Expected results:
there are different formats for a reason, the decision to use
any of them must be show by virt-manager itself. 

Additional info:

Comment 1 Cole Robinson 2012-01-18 15:53:11 UTC

Thanks for the report. However disk image format choice doesn't have anything to do with OS choice. We use raw by default because it is the safest default: older versions of qemu had data integrity issues with qcow2.

Also, you can always create a qcow2 image with the 'use managed or existing storage' option in the new vm wizard.

Long term we may change the default to qcow2 but it will require some work.