StepBee commented on issue #6807: URL: https://github.com/apache/cloudstack/issues/6807#issuecomment-1286923816
@DaanHoogland i still could be totally wrong with my assumptions and i am missing something different, but thats the difference i see at the moment. I didn't dare the stop the other VM, which is running on 8 vCPU and try to start the VM again - as it's a production VM. Your summary is not quite correct. - It looks like before 4.17.0.1 we could create VMs with custom constrained service offerings with more than 2 vCPUs - since 4.17.0.1 we can't create and run VMs with custom constrained service offering with more than 2 vCPUs anymore - since 4.17.0.1 we still can create and start a VM with custom constrained service offering with 2 vCPUs and during runtime dynamically scale the number of vCPUs to above 2, with the OS seeing and using them. But this VM will not start anymore if stopped via cloudstack once, complaining with the described qemu error - But still since 4.17.0.1 we are able to create and start VMs based on fixed service offerings with more than 2 vCPUs -- 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]
