Bug 967643

Summary:	consider filling in cache= and io= on new installs
Product:	[Fedora] Fedora	Reporter:	Kevin Fenzi <kevin>
Component:	virt-manager	Assignee:	Cole Robinson <crobinso>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	20	CC:	berrange, crobinso, hbrock, jforbes, kparal, virt-maint
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	virt-manager-0.10.0-4.git79196cdf.fc20	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-10-15 06:34:09 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Kevin Fenzi 2013-05-27 18:36:10 UTC

For virtual disks you can specify cache and io to use, it would be great if: 

a) New guests got the defaults filled in there so people could see that they could adjust them. 

b) virt-install could see if the storage pool was lvm say and set it to cache=none, io=native or if it was a qcow2/raw file it could be cache=writeback or the best options there.

Comment 1 Fedora End Of Life 2013-09-16 14:01:54 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle.
Changing version to '20'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20

Comment 2 Cole Robinson 2013-10-02 20:14:09 UTC

Upstream sets cache=none and io=native for block devices now.

One problem with encoding the the current writeback default in the XML is that if qemu ever changes its defaults, we are stuck with the old one. Would be nice if libvirt hade a cache=hvdefault setting or similar here but they tend to avoid those things.

Comment 3 Fedora Update System 2013-10-06 19:58:59 UTC

virt-manager-0.10.0-4.git79196cdf.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/virt-manager-0.10.0-4.git79196cdf.fc20

Comment 4 Fedora Update System 2013-10-07 15:47:17 UTC

Package virt-manager-0.10.0-4.git79196cdf.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing virt-manager-0.10.0-4.git79196cdf.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-18473/virt-manager-0.10.0-4.git79196cdf.fc20
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2013-10-15 06:34:09 UTC

virt-manager-0.10.0-4.git79196cdf.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.