Does Xen support this or would it be KVM specific for now?
On Feb 15, 2013 6:04 PM, "edison su (JIRA)" <[email protected]> wrote:

>
>     [
> https://issues.apache.org/jira/browse/CLOUDSTACK-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579654#comment-13579654]
>
> edison su commented on CLOUDSTACK-1302:
> ---------------------------------------
>
> We can add an option in disk offering: e.g. cache policy, has options like
> none/writeback/writethrough, or just safety vs performace(this is what
> vmware did:
> http://pubs.vmware.com/vsphere-4-esx-vcenter/index.jsp?topic=/com.vmware.vsphere.webaccess.doc_41/managing_virtual_machines/t_customize_the_new_virtual_disk.html
> )
>
> > 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
> >            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 is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA
> administrators
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>

Reply via email to