> Can you elaborate more about fresh check=true/false? Does it mean that when it is false ACS is just reading the already created file? And if it is true ACS is creating the file on VR?
Yes, the results are saved in the VR /root/advanced_monitor_results.json /root/basic_monitor_results.json > So false is faster but outdated? yes. > We do not want to use memory ballooning / memory overprovisioning. Is there a global setting in ACS or do we need to add vm.memballoon.disable=true to each agent.properties? > Any downside effects if we do this? As far as I understand documentation dynamic scaling is not effected by this setting. if you do not use memory overprovisioning, the setting might not matter. I am not sure dynamic scaling works or not if memory ballooning is disabled. Please test it. -Wei On Tue, Jan 21, 2025 at 11:41 AM <m...@swen.io> wrote: > Thx, Wei! > > > fresh check=true: run health check again in VR and get the results from > files fresh check=false: get the results from files in VR in most cases, > ACS just gets the health check result, it is much faster. > you can trigger a fresh check by cmk/cloudmonkey. > > Can you elaborate more about fresh check=true/false? Does it mean that > when it is false ACS is just reading the already created file? And if it is > true ACS is creating the file on VR? So false is faster but outdated? > > > The warning "Couldn't retrieve free memory" is because libvirt cannot > get the real memory usage of the VM. > If you want to have accurate memory usage, you can set > vm.memballoon.stats.period in agent.properties refer to > https://docs.cloudstack.apache.org/en/latest/adminguide/hosts.html#id5 > > We do not want to use memory ballooning / memory overprovisioning. Is > there a global setting in ACS or do we need to add > vm.memballoon.disable=true to each agent.properties? Any downside effects > if we do this? As far as I understand documentation dynamic scaling is not > effected by this setting. > > Regards, > Swen > > -----Ursprüngliche Nachricht----- > Von: Wei ZHOU <ustcweiz...@gmail.com> > Gesendet: Dienstag, 21. Januar 2025 10:29 > An: users@cloudstack.apache.org > Betreff: Re: Fetching health check result / Couldn't retrieve free memory > in agent.log > > Hi Swen, > > fresh check=true: run health check again in VR and get the results from > files fresh check=false: get the results from files in VR in most cases, > ACS just gets the health check result, it is much faster. > you can trigger a fresh check by cmk/cloudmonkey. > > > The warning "Couldn't retrieve free memory" is because libvirt cannot get > the real memory usage of the VM. > If you want to have accurate memory usage, you can set > vm.memballoon.stats.period in agent.properties refer to > https://docs.cloudstack.apache.org/en/latest/adminguide/hosts.html#id5 > > -Wei > > > > On Tue, Jan 21, 2025 at 9:15 AM <m...@swen.io> wrote: > > > Hello, > > > > > > > > we run KVM on Ubuntu 22.04 LTS and Ubuntu 24.04 LTS with CS version > > 4.19.1.2 > > at the moment. > > > > > > > > I get the following log entries in the agent.log on all KVM host (IP > > differs, of course): > > > > 2025-01-21 09:01:44,102 INFO > > [resource.virtualnetwork.VirtualRoutingResource] > > (agentRequest-Handler-4:null) (logid:5415bf9a) Fetching health check > > result for 169.254.133.251 and executing fresh checks: false > > > > > > > > All are labeled as INFO. As far as I understand those are health > > checks for virtual routers, but why does it say false? > > > > > > > > > > > > We also get the following warnings: > > > > 2025-01-21 00:29:40,138 WARN [kvm.resource.LibvirtComputingResource] > > (agentRequest-Handler-1:null) (logid:ef5565fb) Couldn't retrieve free > > memory, returning -1. > > > > > > > > Any idea what this means? > > > > > > > > Regards, > > > > Swen > > > > > > >
