[
https://issues.apache.org/jira/browse/CLOUDSTACK-6334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13959223#comment-13959223
]
Marcus Sorensen commented on CLOUDSTACK-6334:
---------------------------------------------
It's definitely a memory issue. It's being launched with ~66MB of RAM:
<currentMemory unit='KiB'>67560</currentMemory>
You need 128 or so to run it. So it sounds like you're setting overprovisioning
to 2 or so?
I checked the 4.3 code, it looks like this should not be happening if your
/etc/cloudstack/agent/agent.properties file contains
"vm.memballoon.disable=true". The applicable code is the same we are running.
You did stop/start the VM after the agent change/restart to get a new
definition, right?
> 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)
