rohityadavcloud commented on issue #7430: URL: https://github.com/apache/cloudstack/issues/7430#issuecomment-1663255968
Hi, sorry to join the party late. I found this is a feature and not a bug, probably needs better documentation cc @weizhouapache @DaanHoogland @rajujith (the fix may be still valid if we don't want to revert). By default, the VM memory balloon feature is enabled for KVM, https://github.com/apache/cloudstack/blob/main/agent/conf/agent.properties#L220 so if the memory overcommit is > 1, CloudStack assumes the guest have necessary drives and starts the VMs with the minimum memory (which is allocated memory divided by the memory overprovisioning factor) and assumes the guest can dynamically request for more memory. To have the VMs start with the allocated memory by default, for example if ksm or memory compression etc options are enabled on the host; then simply add the setting `vm.memballoon.disable=true` in agent.properties on kvm hosts when memory overprovisioning is > 1 and VMs will start with allocated memory (not cause panic) and you've overcommitted memory. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
