[
https://issues.apache.org/jira/browse/CLOUDSTACK-6334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13959294#comment-13959294
]
Marcus Sorensen commented on CLOUDSTACK-6334:
---------------------------------------------
Not the agent. The VM. The VM needs to be stopped/started after the agent has
the setting updated. It's possible that it might work under some circumstances
with currentMemory=64M, but it won't reliably work. I really don't see how you
can get a currentMemory setting that is different from the memory one at all if
you start a new VM after setting that agent.properties setting. It will also
only add the line "<memballoon model='virtio'>" if that setting is
non-existent, otherwise you get "<memballoon model='none'>".
These suggest that either the VM hasn't been stopped/started after the agent
conf change, or the agent itself isn't 4.3 code.
> 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)
