Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1097D10799 for ; Thu, 5 Dec 2013 23:16:36 +0000 (UTC) Received: (qmail 76715 invoked by uid 500); 5 Dec 2013 23:16:35 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 76702 invoked by uid 500); 5 Dec 2013 23:16:35 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 76694 invoked by uid 500); 5 Dec 2013 23:16:35 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 76691 invoked by uid 99); 5 Dec 2013 23:16:35 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Dec 2013 23:16:35 +0000 Date: Thu, 5 Dec 2013 23:16:35 +0000 (UTC) From: "Nitin Mehta (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CLOUDSTACK-5391) Change service offering of a stopped vm and then starting it should check host cpu capability MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-5391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-5391: ------------------------------------ Description: 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. was:Change service offering of a stopped vm and then starting it should check host cpu capability with the new service offering. > 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)