Hi, Can you perform the same steps again ? If the result is same, you can create an issue on github: https://github.com/apache/cloudstack/issues/new
-Wei On Mon, 19 Feb 2024 at 10:30, Bharat Bhushan Saini <bharat.sa...@kloudspot.com.invalid> wrote: > Hi Wei, > > > > First I did poweroff from inside the vm the it is going off but the status > show that it is running then I do turned off from the UI as well then > status shows in UI stopped > > > > Thanks and Regards, > > Bharat Saini > > > > [image: signature_615347824] > > > > *From: *Wei ZHOU <ustcweiz...@gmail.com> > *Date: *Monday, 19 February 2024 at 2:45 PM > *To: *users@cloudstack.apache.org <users@cloudstack.apache.org> > *Subject: *Re: CPU Core Consumption High > > EXTERNAL EMAIL: Please verify the sender email address before taking any > action, replying, clicking any link or opening any attachment. > > > Hi, > > Did you poweroff from inside the VM or on cloudstack UI ? > > -Wei > > On Mon, 19 Feb 2024 at 09:53, Bharat Bhushan Saini > <bharat.sa...@kloudspot.com.invalid> wrote: > > > Hi Wei/Darren, > > > > > > > > The issue was again trigged after the enable the > resource.count.running.vms.only > > option. > > I shut down all the vm’s but the resource utilization is same as before > > when vm’s are running. > > > > > > > > Thanks and Regards, > > > > Bharat Saini > > > > > > > > [image: signature_2781584380] > > > > > > > > *From: *Wei ZHOU <ustcweiz...@gmail.com> > > *Date: *Tuesday, 13 February 2024 at 12:59 AM > > *To: *users@cloudstack.apache.org <users@cloudstack.apache.org> > > *Subject: *Re: CPU Core Consumption High > > > > EXTERNAL EMAIL: Please verify the sender email address before taking any > > action, replying, clicking any link or opening any attachment. > > > > > > +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. > > > > > > > --------------------------- 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. > > > > --------------------------- 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. >
