You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cloudstack.apache.org by "Koushik Das (JIRA)" <ji...@apache.org> on 2015/05/01 08:39:06 UTC

[jira] [Created] (CLOUDSTACK-8438) Proper enforcement of hypervisor capability "max. guest limit"

Koushik Das created CLOUDSTACK-8438:
---------------------------------------

             Summary: Proper enforcement of hypervisor capability "max. guest limit"
                 Key: CLOUDSTACK-8438
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8438
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Management Server
    Affects Versions: 4.5.0
            Reporter: Koushik Das
            Assignee: Koushik Das
             Fix For: 4.6.0


Currently only the VMs in 'Running' state are considered for enforcing "max. guest limit". There is a flaw in this approach. If there are parallel VM deployments happening then there is a possibility that the HV host may end up having more VMs than the limit.

Fix would be consider VMs in transition states as well for enforcing limit. These are Starting, Stopping, Migrating.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)