You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/12/05 23:15:36 UTC

[jira] [Commented] (CLOUDSTACK-4880) VM's CPUs getting scaled up above host capacity (Without any migration to other host)

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-4880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13840631#comment-13840631 ] 

ASF subversion and git services commented on CLOUDSTACK-4880:
-------------------------------------------------------------

Commit 1cdc064c438d155bedf451fab37b76a4b0a9773b in branch refs/heads/4.3 from [~nitinme]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=1cdc064 ]

CLOUDSTACK-4880:
check for host cpu capability while dynamic scaling a vm on the same host


> VM's CPUs getting scaled up above host capacity (Without any migration to other host)
> -------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4880
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4880
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Automation
>    Affects Versions: 4.3.0
>         Environment: Observed on XenServer yet.
>            Reporter: Gaurav Aradhye
>            Assignee: Nitin Mehta
>            Priority: Critical
>             Fix For: 4.3.0
>
>
> Host has 4 physical CPU cores.
> Create a service offering of 5 CPU cores and scaled up existing VM with this service offering. The operation was successful.
> I was even able to reboot the instance.
> However no new instance could be launched using this service offering which seems to be a valid behavior.



--
This message was sent by Atlassian JIRA
(v6.1#6144)