[
https://issues.apache.org/jira/browse/CLOUDSTACK-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13828582#comment-13828582
]
ASF subversion and git services commented on CLOUDSTACK-1302:
-------------------------------------------------------------
Commit 7f1168cec74c704257f2d6040cd352b240d5d299 in branch refs/heads/master
from [~widodh]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7f1168c ]
CLOUDSTACK-1302: Add cache mode to SQL upgrade file
This got lost in the previous commit
Not sure though if this is the right file, since this feature won't make it into
4.3, but there is no 4.4 file.
> 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
>
> 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.1#6144)