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/07/23 01:08:49 UTC
[jira] [Commented] (CLOUDSTACK-2990) [ UI ] After scaling up
,increased memory and cpu is not getting registered in guest OS
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715826#comment-13715826 ]
ASF subversion and git services commented on CLOUDSTACK-2990:
-------------------------------------------------------------
Commit c2faa0906897b9f745f65cb7f62eccf8bb431a4c in branch refs/heads/4.2 from [~bfederle]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c2faa09 ]
CLOUDSTACK-2990: Before scape-up, present prompt to user if on VMware
> [ UI ] After scaling up ,increased memory and cpu is not getting registered in guest OS
> ------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-2990
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2990
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: UI
> Affects Versions: 4.2.0
> Environment: Hypervisor Esxi 5.1
> Reporter: prashant kumar mishra
> Assignee: Brian Federle
> Priority: Critical
> Fix For: 4.2.0
>
>
> Guest OS :"CentOS 5.3(64-bit) no GUI (vSphere)" Default template.
> Steps to reproduce
> -----------------------------
> 1-Deploy a vm with SO small ( RAM :512 MB,CPU 500MHz)
> 2-Scale up to SO medium (RAM:1024MB,CPU 1000MHz)
> Expected
> --------------
> Guest OS should be able to use increased memory and cpu
> Actual
> -----------
> Guest OS still shows old( before scale up) memory and cpu values
> My observation
> -----------------------
> -On xen server increased memory and cpu is getting registered in Guest OS after scale up
--
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