[jira] [Commented] (CLOUDSTACK-7545) [VMware] DiskIOLimitation from ComputeOffering and DiskOffering doesn't apply to VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14151456#comment-14151456 ] Axel Delahaye commented on CLOUDSTACK-7545: --- Are you interested in an implementation for VmWare ? [VMware] DiskIOLimitation from ComputeOffering and DiskOffering doesn't apply to VM --- Key: CLOUDSTACK-7545 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7545 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.3.0 Environment: Vmware Vcenter 5.5 Reporter: Axel Delahaye Priority: Critical Labels: iops, vmware When I set up an iops limit to the ComputeOffering or the DiskOffering. After start a VM and looking in the vCenter web client, all disks of the VM are set to Unlimited IOPS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7545) [VMware] DiskIOLimitation from ComputeOffering and DiskOffering doesn't apply to VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14133786#comment-14133786 ] Wei Zhou commented on CLOUDSTACK-7545: -- This functionality only works on KVM (not implemented for VmWare/XenServer) [VMware] DiskIOLimitation from ComputeOffering and DiskOffering doesn't apply to VM --- Key: CLOUDSTACK-7545 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7545 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.3.0 Environment: Vmware Vcenter 5.5 Reporter: Axel Delahaye Priority: Critical Labels: iops, vmware When I set up an iops limit to the ComputeOffering or the DiskOffering. After start a VM and looking in the vCenter web client, all disks of the VM are set to Unlimited IOPS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
