GutoVeronezi commented on issue #6865: URL: https://github.com/apache/cloudstack/issues/6865#issuecomment-1386334137
Hello @1450793561 @weizhouapache KVM requires defining ranges for CPU and memory in the VM XML to allow the VM to be dynamically scaled. Currently, those ranges are set only when working with custom compute offerings. For custom-constrained offerings, the ranges are defined while creating them; for custom-unconstrained offerings, the ranges are defined via the global settings `vm.serviceoffering.cpu.cores.max` and `vm.serviceoffering.ram.size.max`, or, if the settings are `0`, they are defined according to the host capacities. As KVM supports dynamic scaling, this situation is a matter of designing the logical solution in ACS. We are planning to extend ACS to allow dynamic scaling VMs with fixed offerings in KVM; however, we do not have a due date yet. --- @1450793561, while a VM with fixed offering cannot be dynamically scaled yet, you could try using custom offerings. Along with the custom offerings, some configurations have to be done: - in the global settings, `enable.dynamic.scale.vm` must be `true`; - the template and the VM must be marked as `Dynamically scalable`; VMs started after setting those configurations will be able to be dynamically scaled. If you have any doubts or issues using this alternative, just ping me in this issue. -- 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: commits-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
