[
https://issues.apache.org/jira/browse/CLOUDSTACK-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14521659#comment-14521659
]
ASF subversion and git services commented on CLOUDSTACK-1302:
-------------------------------------------------------------
Commit 10c1deb1892d3eb8b1d20a2c2cd7fc6c7a9e6902 in cloudstack's branch
refs/heads/CLOUDSTACK-1302 from [~widodh]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=10c1deb ]
CLOUDSTACK-1302: Fix passing cacheMode to hypervisor
The cacheMode setting was not being set from the UI, but it was also
not passed to the Hypervisor when it was set manually in the database.
> 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)
