You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Koushik Das (JIRA)" <ji...@apache.org> on 2014/06/04 11:28:03 UTC
[jira] [Commented] (CLOUDSTACK-5205) System vm startup scripts
calculate jvm memory wrong
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14017523#comment-14017523 ]
Koushik Das commented on CLOUDSTACK-5205:
-----------------------------------------
This is fixed on 4.3 and above with this commit.
commit 4809d91c51ce682f3e18d85fb4e6318b27fac2a7
Author: Koushik Das <ko...@apache.org>
Date: Fri Jan 31 10:35:19 2014 +0530
CLOUDSTACK-5993: Cloud agent fails to start on 32-bit system vms (cpvm and ssvm) created with 4GB RAM offering
Capped the max heap size of the JVM at 2600M for 32-bit system VMs. For 64-bit, existing logic works fine.
(cherry picked from commit 1ae02009b562692a7da54f2694a9962f55660aa3)
Signed-off-by: Animesh Chaturvedi <an...@apache.org>
> System vm startup scripts calculate jvm memory wrong
> ----------------------------------------------------
>
> Key: CLOUDSTACK-5205
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5205
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: SystemVM
> Affects Versions: 4.2.0
> Reporter: John E Vincent
> Assignee: Koushik Das
> Fix For: 4.3.0, 4.4.0
>
>
> While attempting to provision beefier system vms, we discovered this bug.
> The `_run.sh` script in the system vm calculates jvm memory based on 80% of the total memory on the system. This is great up until the point 80% of memory goes above ~1.9G. The system vm templates are all 32-bit and so calculating the size too high will cause the agent jvm to fail to start.
> The fix is pretty simple with a final sanity check:
> if [ $maxmem -gt 1900 ]
> then
> maxmem=1900
> fi
--
This message was sent by Atlassian JIRA
(v6.2#6252)