Bug 623188

Summary: Defaults to using cache with an LVM backed storage.
Product: [Community] Virtualization Tools Reporter: Jamin W. Collins <jcollins>
Component: virt-managerAssignee: Libvirt Maintainers <libvirt-maint>
Severity: medium Docs Contact:
Priority: low    
Version: unspecifiedCC: ayers, berrange, crobinso, xen-maint
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-02 20:12:51 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 Jamin W. Collins 2010-08-11 14:43:39 UTC
Description of problem:
Defaults to using cache with an LVM backed storage.  The use of caching with raw partitions (LVM) results in significantly lower performance than no cache at all.

How reproducible:

Steps to Reproduce:
1. Create a new VM using LVM backed storage
Actual results:
Cache is enabled for the VM's disks residing within LVM.

Expected results:
Cache should be disabled for disks residing within LVM.

Additional info:


QEMU also supports a wide variety of caching modes. Writeback is useful for testing but does not offer storage guarantees. Writethrough (the default) is safer, and relies on the host cache. If you're using raw volumes or partitions, it is best to avoid the cache completely, which reduces data copies and bus traffic:

 qemu -drive file=/dev/mapper/ImagesVolumeGroup-Guest1,cache=none,if=virtio

This has also been reported with Ubuntu at: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/568445

Comment 1 Daniel Berrangé 2010-08-11 16:12:46 UTC
Choice of caching mode is a policy decision. These belong in virt-manager or other apps using libvirt.

Comment 2 Jamin W. Collins 2010-08-11 17:01:21 UTC
AFAIK, this is the place to post feature requests for virt-manager, at least this is where their website directed me.  Intentionally selecting a default mode that results in very poor performance (about 1/5 less) when the upstream for the virtualization engine (qemu/kvm) clearly indicates that another mode is preferable is (IMHO) a bad choice.  Furthermore, from what I can tell, virt-manager doesn't appear to provide any means of changing or overriding the default.  A user must instead manually edit the server's XML definition of the VM in question.

Comment 3 Jamin W. Collins 2010-08-16 15:38:49 UTC
Reopening against virt-manager as recommended on mailing list.

Comment 4 Cole Robinson 2013-10-02 20:12:51 UTC
Fixed upstream now