[
https://issues.apache.org/jira/browse/CLOUDSTACK-5205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13827404#comment-13827404
]
Prasanna Santhanam commented on CLOUDSTACK-5205:
------------------------------------------------
Thanks! Do you think you can submit a patch for this? Please post it on
reviewboard.apache.org. Patches left in JIRA tickets generally don't get
noticed by the concerned contributors. Here's some guidelines :
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Review+Board+Guidelines
> 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
>
> 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.1#6144)
