DaanHoogland commented on PR #10964: URL: https://github.com/apache/cloudstack/pull/10964#issuecomment-2963698050
> > What is the backwards incompatibilty you fear? > > @DaanHoogland, the backwards incompatibility lies in the fact that the `guest.cpu.features` property is currently used to define CPU flags only for end-user VMs. If we change it to also apply to system VMs, operators would lose the ability to set flags exclusively for end-user VMs. > > > @bernardodemarco , as per your description, would it not make sense to always apply guest.cpu.features to systemvms as well? > > Yes, it would. I can update the PR tomorrow to reflect this. What are your thoughts? I do not know what would be wisdom here. - is a different set of settings needed for VMs and systemVMs? - would you ever want to not apply settings to systemVMs? intiutively, I’d just apply the user VM settings to systemVMs as well. -- 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
