You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "prashant kumar mishra (JIRA)" <ji...@apache.org> on 2013/06/12 08:10:19 UTC
[jira] [Created] (CLOUDSTACK-2939) CPU limit is not getting set for
vm after scaleup to a service offering which have cpu cap enabled
prashant kumar mishra created CLOUDSTACK-2939:
-------------------------------------------------
Summary: CPU limit is not getting set for vm after scaleup to a service offering which have cpu cap enabled
Key: CLOUDSTACK-2939
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2939
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Management Server, VMware
Affects Versions: 4.2.0
Environment: VMware ESXI-5.1
Reporter: prashant kumar mishra
Fix For: 4.2.0
Steps to reproduce
----------------------------
1-Deploye a vm with small service offering (memory:512,cpu:500;cpu cap=not enable)
2-Scaleup to service offering (memory:512,cpu:1000, cpu cap=enable)
Expected
--------------
cpu limit should be set for the vm
Actual
------------
there is no cpu limit for vm
--
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