cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksandr (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-1302) Add per storage setting for cache="none/writeback/writethrough" options for VMs on KVM hypervisor
Date Fri, 24 Apr 2015 23:57:39 GMT

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

Aleksandr commented on CLOUDSTACK-1302:
---------------------------------------

Can someone confirm that this feature was implemented and IS actually working ?
I have CS version 4.4.2, I see this feature in "disk offering options" as Write-cache Type
but I simply cant set it - no matter what I choose  choice will not apply to disk offering.
Some screenshots : http://puu.sh/hpJiY/11889fb414.png and result > http://puu.sh/hpJkk/70a0ebeb79.png
As you can see the " Write-cache Type" remains empty.

Regards,

> 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)

Mime
View raw message