Subscribe to my newsletter, support me on Patreon or by PayPal donation. 8) Use statistical methods to process measurements.3) Set scaling_governor to ‘performance’.So perhaps even though the VM OS may not go into Turbo Boost, the execution of the VM inside ESXi might. TSC: 302386 cpu0:1)BootConfig: 454: disableTurbo = FALSE

The TSC speed would be the base clock speed. The sample below it measures the CPU speed from the High Precision Event Timer (HPET) and reads from the Time Stamp Counter (TSC). The total ESXi host CPU capacity formula (as in seen in the upper right hand when you log in to the ESXi host client) is calculated on the base clock speed and not turbo clock speed. I had to mask out CPUID leaf 6 eax bit 1 to mask out the 'ida' flag. But I suppose the lack of other MSRs would not make the VM take advantage of turbo mode. On a Linux VM, proc/cpuinfo still shows 'ida' in the flags section. I looked at the Windows 10 VM on Workstation Pro 12.5.9 (should be similar to ESXi as the VMs are interchangeable/compatible), using CPU-Z 1.8, the clocks multiplier is also stuck at x1.0 (in the About tab) vs having the a multiplier value on its Windows 10 host.īut I don't think VMware masks out the turbo flag. There is no (virtual) CPU temperature which could play a role whether turbo is turned on or not by the guest OS.

Possibly because the MSR to indicate what clock ratio it is allowed to go up to among a number of other things are likely not implemented/exposed to the virtual CPU/virtual hardware. I don't think Turbo Boost works inside the VM.Īs you have seen from Task Manager, a Windows VM does not see the turbo clock speed either.

How to enable turbo boost on linux