You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Nitin Mehta (JIRA)" <ji...@apache.org> on 2013/12/06 00:28:36 UTC

[jira] [Resolved] (CLOUDSTACK-5391) Change service offering of a stopped vm and then starting it should check host cpu capability

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-5391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nitin Mehta resolved CLOUDSTACK-5391.
-------------------------------------

    Resolution: Fixed

> Change service offering of a stopped vm and then starting it should check host cpu capability
> ---------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-5391
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5391
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.2.0
>            Reporter: Nitin Mehta
>            Assignee: Nitin Mehta
>             Fix For: 4.3.0
>
>
> Change service offering of a stopped vm and then starting it should check host cpu capability with the new service offering.
> Host has 4 physical CPU cores. 
> Create a service offering of 5 CPU cores and scaled up existing VM with this service offering.
> Similarly for speed.



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