Hudratronium commented on issue #6680: URL: https://github.com/apache/cloudstack/issues/6680#issuecomment-1231423029
@shwstppr The behaviour has changed as since the upgrade the reported values "changed" to the current cpu speeds. That hasn't been the case in our installation from 4.15. onwards - including the upgrades / restarts of hosts - thats why i was so suprised. That leaded to a situation that 1. Service Offerings haven't been working anymore (couldn't find useable hosts as the cpu speed was way to low) 2. Migration tasks failed as no suitable hosts were availeable anymore Biggest problem for our usecase: "HA-Features" wouldn't be working in this situation "Workaround" for us was to set the `host.cpu.manual.speed.mhz` option in the agent.conf manually for our hosts. Regarding the outputs for the different checks performed by the agent: 1. LSCPU script seems not to be working with AMD CPUs, as the "speed" isn't part of the name. lscpu would deliver correct values never the less - but one would need to check those / choose the "right" ones 2. File is not availeable under Ubuntu 20.04 - at least for my AMD devices. I could offer something like `cpuinfo_max_freq` :-D 3. The value from libvirt - which seemed to be kind of variable - was way off. As i don't know how / which value is used i can't really give a impression what values are returned. From our findings the scope was between 1,3GHz up to 2,7Ghz. All Hosts with the same CPU Modell and same "host"-configuration. -- 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]
