GutoVeronezi commented on issue #7529: URL: https://github.com/apache/cloudstack/issues/7529#issuecomment-1643884880
Hello @yashi4engg, In the previous conjuncture, when ACS was deploying a VM, it would define a minimum memory|CPU to the VM based on a calculation through the overprovisioning (`defined mem|cpu speed` / `overprovisioning factor`); Therefore, it would define a range of memory/CPU, even if it did not use scalable (dynamic) service offerings. To workaround this situation, configurations `vm.min.memory.equals.memory.divided.by.mem.overprovisioning.factor` and `vm.min.cpu.speed.equals.cpu.speed.divided.by.cpu.overprovisioning.factor` were introduced (with PR #4722), to allow operators decide if they want the minimum memory|CPU to be different from the allocated value when the overprovisioning's configurations are different than 1. By default these configurations are `true`, to keep the initial behavior; however, in your case, you should mark those configurations as `false`, so the memory|speed allocated to the VM is the actual defined in the offering. Could you apply the suggestion and make some tests? Best regards -- 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]
