[ https://issues.apache.org/jira/browse/CLOUDSTACK-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15286353#comment-15286353 ]
Andrei Mikhailovsky commented on CLOUDSTACK-1302: ------------------------------------------------- Hello guys, As far as I can tell for myself and a few people from the user mailing list also confirmed this, setting the cache option under the disk service offering does NOTHING to the cache=none string when launching a vm under KVM. I've tried setting the cache value to multiple values. The cache=none is still shown in ps aux when a vm is launched. This applies to both the root and the data disks. > Add per storage setting for cache="none/writeback/writethrough" options for > VMs on KVM hypervisor > ------------------------------------------------------------------------------------------------- > > Key: CLOUDSTACK-1302 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1302 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server > Affects Versions: 4.0.0 > Environment: Ubuntu 12.04.2 Host, KVM hypervisor > Reporter: Jason Villalta > Assignee: Wido den Hollander > Priority: Minor > Fix For: 4.4.0, 4.5.0 > > > Version 4.0.0 of Cloudstack has a hard coded value of cache=none for virtual > machines deployed. This causes conflict with filesystems mounted with fuse > such as ZFS, GlusterFs and CEPH as fuse does not support directio with these > file systems. When starting VMs libvirt throws an error "could not open disk > image <disk> Invalid argument" > Changing the cache= setting to writethough or writeback solves this problem > but there currently is no way to set this. Ideally this would get set on a > per datastore basis. -- This message was sent by Atlassian JIRA (v6.3.4#6332)