[jira] [Comment Edited] (CLOUDSTACK-1302) Add per storage setting for cache="none/writeback/writethrough" options for VMs on KVM hypervisor

["Wido den Hollander (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14520148#comment-14520148 ] 

Wido den Hollander edited comment on CLOUDSTACK-1302 at 4/29/15 8:41 PM:
-------------------------------------------------------------------------

Got my hardware up and running earlier then expected. I can confirm that this is indeed not working properly. The cache setting stays NULL in the database.

This seems like an issue with the UI and setting it actually. Can you try to set it manually in the database and see if that works?


was (Author: widodh):
Got my hardware up and running earlier then expected. I can confirm that this is indeed not working properly. The cache setting stays NULL 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)