StepBee commented on issue #6807: URL: https://github.com/apache/cloudstack/issues/6807#issuecomment-1289486239
Just found the cause: enable.dynamic.scale.vm = true In our staging environment, this setting is set to "false". I remember we activated this setting somewhere around the time when we did the update. Whats **working**: ``` enable.dynamic.scale.vm = **true** and having a **custom** serviceoffering with **disabled** dynamic scaling ``` or ``` enable.dynamic.scale.vm = **false** and having a **custom** serviceoffering with **enabled** dynamic scaling (because it has no effect) ``` or ``` enable.dynamic.scale.vm = **true** and having a **fixed** serviceoffering with **enabled** dynamic scaling ``` or `using a VM template with disabled dynamic scaling` Whats **not working** ``` enable.dynamic.scale.vm = **true** and having a serviceoffering with **enabled** dynamic scaling and having a vm template with ***enabled** dynamic scaling ``` So enabled dynamical scaling (in global settings AND service offering AND vm template) on **KVM** is responsible for the missing cpu topology line in the qemu xml, which will then result in qemu not starting the VM. Now the question: Is this how it is supposed to be or is this a bug? -- 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]
