[
https://issues.apache.org/jira/browse/CLOUDSTACK-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661925#comment-13661925
]
ASF subversion and git services commented on CLOUDSTACK-2085:
-------------------------------------------------------------
Commit 8da7ec05f1c7dae0aab827ae0568e120111c6579 in branch refs/heads/master
from [~tsp]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=8da7ec0 ]
CLOUDSTACK-2085: DMC enable guest scaling
When dmc is enabled allow cloudstack to scale the VM between dynamic
ranges. This requires a further commit where there is enough memory
available between dynamic-max and static-max for the VM to scale under
memory pressure. See the TODO in Xenserver56FP1Resource.java
Signed-off-by: Prasanna Santhanam <[email protected]>
> VM weight on xen remain same as before vmscaleup ;because
> "Add-To-VCPUs-Params-Live.sh" is not getting copied on xs host
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-2085
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2085
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.2.0
> Reporter: prashant kumar mishra
> Assignee: Harikrishna Patnala
> Priority: Critical
> Fix For: 4.2.0
>
>
> Hypervisor Xen
> Commit "2057221f4f1fd5afde422b367fc416d4e44275cb"
> VM weight on xen is not getting changed after scaleup
> Step to reproduce
> ----------------------------
> 1-Deployed a vm with service offering "small instance" (weight on xen 52) ,
> 2-Scaled up vm to service offering medium instance
> Expected
> -------------
> after scale up VM should get weight according to new service offering
> Actual
> ---------
> VM weight remain same as before scale up
> Work around
> -------------------
> copy script "Add-To-VCPUs-Params-Live.sh" to /opt/xensource/bin
--
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
