Re: KVM wrong CPU speed reported

2018-12-28 Thread Ivan Kudryavtsev
Fixing that is not back compatible because SOs can be created aligned to TurboBoost values. Adding global variable switch can be an option. пт, 28 дек. 2018 г., 7:38 Andrija Panic andrija.pa...@gmail.com: > I agree Wido, it's just that it's wrong - there should be no implicit CPU > over-provision

Re: KVM wrong CPU speed reported

2018-12-28 Thread Andrija Panic
I agree Wido, it's just that it's wrong - there should be no implicit CPU over-provisioning by default - and yes, later you can do over-provision by 2-3 as most of us do... just something that hurts my eyes :) On Fri, 28 Dec 2018 at 11:39, Wido den Hollander wrote: > > > On 12/28/18 9:23 AM, And

Re: KVM wrong CPU speed reported

2018-12-28 Thread Wido den Hollander
On 12/28/18 9:23 AM, Andrija Panic wrote: > Hi guys, > > https://github.com/apache/cloudstack/commit/29e389eb872ffa816be99aa66ff20bdec56d3187 > > this one gets above gets CPU frequency with "effectively > "cat sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq" which gives the > TurboBoost C