+1. The setting was introduced in 4.14 by my PR https://github.com/apache/cloudstack/pull/3760 However, to keep backwards compatibility, the default value was set to false, which does not make sense IMHO.
-Wei 在 2024年2月12日星期一，Darren Cole <dc...@aseg.com.invalid> 写道： > This caught me before as well. > By default resource.count.running.vms.only is set to false, so resources > are counted for all VMs. > On clusters I run I set this to true so that only running VMs are counted > for resource use. > > I have not tested 4.19 yet, but assume the setting stayed the same. > There are also some similar/related settings to determine how running > resources are counted. > Some of these are specific what is backing the VMs. > ie KVM, Xen, etc. > > Darren > -- > This e-mail is confidential. Any distribution, use or copying of this > e-mail or the information it contains other than by the intended recipient > is forbidden. If you are not the intended recipient, please advise the > sender (by return e-mail or otherwise) immediately and delete this e-mail. > > > From: "Bharat Bhushan Saini" <bharat.sa...@kloudspot.com.INVALID> > To: "users" <users@cloudstack.apache.org> > Sent: Sunday, February 11, 2024 11:14:58 PM > Subject: CPU Core Consumption High > > > > Hi All, > > > > I am facing an issue regarding the core consumption by the cloudstack. I > started 2 vm with 6 cores and it takes 18 cores but when I poweroff the vm > the cores remains same in the dashboard. > > > > > Thanks and Regards, > > Bharat Saini > > > > > > > --------------------------- Disclaimer: ------------------------------ > This message and its contents are intended solely for the designated > addressee and are proprietary to Kloudspot. The information in this email > is meant exclusively for Kloudspot business use. Any use by individuals > other than the addressee constitutes misuse and an infringement of > Kloudspot's proprietary rights. If you are not the intended recipient, > please return this email to the sender. Kloudspot cannot guarantee the > security or error-free transmission of e-mail communications. Information > could be intercepted, corrupted, lost, destroyed, arrive late or > incomplete, or contain viruses. Therefore, Kloudspot shall not be liable > for any issues arising from the transmission of this email. >
