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/07/05 06:43:48 UTC
[jira] [Updated] (CLOUDSTACK-1695) Not enough cpu avialable in
cluster according to new overcommit ratio but all stopped Vms can be
started without any failure(required cpu for stopped vm is > > available
cpu )
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
prashant kumar mishra updated CLOUDSTACK-1695:
----------------------------------------------
Attachment: DB_logs.rar
> Not enough cpu avialable in cluster according to new overcommit ratio but all stopped Vms can be started without any failure(required cpu for stopped vm is > > available cpu )
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-1695
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1695
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Affects Versions: 4.2.0
> Environment: XEN,KVM Branch Master
> Reporter: prashant kumar mishra
> Assignee: Bharat Kumar
> Fix For: 4.2.0
>
> Attachments: DB_logs.rar
>
>
> After Stop/Destroy , vms can be successfully start/Restore-start only when enough resources are available based on current overcommit ratio, .
> Step to Reproduce
> -----------------------------
> 1-Set cpu overcommit ratio to 4
> 2-Deploy vms such that no cpu left in cluster
> 3-change overcommit ratio to 1
> 4-Stop/Destroy all the vms
> 5-Start/restore-start all vms
> Expected Result
> -------------------------
> only few vms should come up ,since there is less resource(overcommit ratio=1) available than before (when overcommit ratio was 4)
> Actual
> ----------------
> All vm stopped/Destroyed in step 4 came up without any failure
--
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