[
https://issues.apache.org/jira/browse/CLOUDSTACK-6334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13959085#comment-13959085
]
Marcus Sorensen commented on CLOUDSTACK-6334:
---------------------------------------------
Try vm.memballoon.disable=true in the agent.properties. The issue was that
memory overprovisioning works... strangely. Setting it to greater than 1
actually divides the RAM spec by that amount, leaving small VMs like system VMs
unable to boot. The idea, I think, is to make it adjustable in an upward
direction if there is capacity on the host, but doesn't take into account
memory deduplication.
> Issue is Reproduceable - Suggest Re-open
> -----------------------------------------
>
> Key: CLOUDSTACK-6334
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6334
> Project: CloudStack
> Issue Type: Sub-task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Virtual Router
> Affects Versions: 4.3.0
> Environment: CentOS - KVM
> Reporter: Prieur Leary
> Fix For: 4.2.0
>
>
> This is issue is reproducable when setting the cluster property
> mem.overprovisioning.factor greater than 1.
> If the virtual router is started or re-started and the variable is set
> greater than one, the Virtual Router VM is created on the host, but never
> boots.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
