[
https://issues.apache.org/jira/browse/CLOUDSTACK-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13829157#comment-13829157
]
ASF subversion and git services commented on CLOUDSTACK-1302:
-------------------------------------------------------------
Commit 308b7a5c37e4af20315b68254140195948552e23 in branch refs/heads/master
from [~widodh]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=308b7a5 ]
CLOUDSTACK-1302: Allow cache_mode to be NULL in the database
Not allowing this field to be NULL broke master due to the default
data which gets loaded into the database during initial startup of the
management server.
During generation of the XML for the VM it will however default to
'none' if NULL is passed
> 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)
