Failed to Get Cpufreq Parameter (Doc ID 2546200.1)

Last updated on JANUARY 01, 2024

Applies to:

Symptoms

The Xen hypervisor offers a mechanism to balance performance and power consumption through CPU frequency scaling. Known as the Current Governor, this mechanism can lower power consumption by throttling the clock speed when a CPU is idle.

Certain versions of Oracle VM Server have the Current Governor set to ondemand by default, which dynamically scales the CPU clock based on the load. Oracle recommends that on Oracle nodes you run the Current Governor with the performance setting. Particularly if you find that systems are not performing as expected after an upgrade of Oracle VM Server, make sure that the Current Governor is configured correctly.

To verify the Current Governor setting of a compute node, log in using SSH and enter the following command at the Oracle Linux prompt:

[root@XXX ~]# xenpm get-cpufreq-para|grep current_governor
[CPU0] failed to get cpufreq parameter
[CPU1] failed to get cpufreq parameter
[CPU2] failed to get cpufreq parameter
[CPU3] failed to get cpufreq parameter
[CPU4] failed to get cpufreq parameter
[CPU5] failed to get cpufreq parameter
[CPU6] failed to get cpufreq parameter
[CPU7] failed to get cpufreq parameter
[CPU8] failed to get cpufreq parameter

Changes

 No changes.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.