Red Hat Bugzilla – Bug 1443182
cpu-partitioning: ERROR tuned.utils.commands: Executing x86_energy_perf_policy error
Last modified: 2018-04-10 12:01:26 EDT
Description of problem: I see the following in /var/log/tuned/tuned.log when activating the cpu-partitioning profile in a KVM guest: 2017-04-18 09:56:00,703 ERROR tuned.utils.commands: Executing x86_energy_perf_policy error: 2017-04-18 09:56:00,703 WARNING tuned.plugins.plugin_cpu: your CPU doesn't support MSR_IA32_ENERGY_PERF_BIAS, ignoring CPU energy performance bias It is possible that MSR_IA32_ENERGY_PERF_BIAS is not emulated by KVM. Version-Release number of selected component (if applicable): tuned-2.8.0-2.el7 How reproducible: Steps to Reproduce: 1. Activate the cpu-partitioning profile 2. Check /var/log/tuned/tuned.log
Jaroslav, I think this problem has always existed and doesn't cause any problems for zero-loss (meaning, the zero-loss tuning is still being applied). In that case, this can be moved to 7.5.
Yes, it's not regression. Maybe we could consolidate the related log messages to be both in WARN level or maybe we could lower the level to NOTICE.
I think the perfect solution would be to test if the CPU supports the MSR_IA32_ENERGY_PERF_BIAS MSR (or any other way to test if the tuning could be applied). Then: - If the MSR is not supported, just print the message as a NOTICE - If the MSR is supported but applying the tuning fails, fail with ERROR Anyways, moving to 7.5.
I propose we completely suppress the ERROR message and keep the second message as WARN. I think we should keep the second message as WARN, otherwise the problem could go unnoticed. I think we usually log a warning when something is not supported: tuned/plugins/plugin_video.py: log.warn("radeon_powersave is not supported on '%s'" % device) tuned/plugins/plugin_vm.py: log.warn("Option 'transparent_hugepages' is not supported on current hardware.") Upstream pull request: https://github.com/redhat-performance/tuned/pull/62
Upstream: https://github.com/redhat-performance/tuned/commit/43c1b819d31355715c3a8a0513e436f5e6f5fe94
That makes sense, thanks for fixing this Ondrej.
tuned-2.9.0-0.1.rc1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-d9c6b990df
tuned-2.9.0-0.1.rc1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-d9c6b990df
tuned-2.9.0-0.1.rc1.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-5f0849d207
tuned-2.9.0-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-0e45ce4685
tuned-2.9.0-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-c30e9bd1ea
I verified this BZ. In tuned-2.9.0-1.el7.noarch the ERROR message is gone and, apart from the INFO lines, I only have: 2018-01-22 16:43:43,257 WARNING tuned.plugins.plugin_cpu: your CPU doesn't support MSR_IA32_ENERGY_PERF_BIAS, ignoring CPU energy performance bias Which is fine, according to comment 5, is expected.
Hi Luiz, thank you for your testing. Verified in tuned-2.9.0-1.el7.noarch * patch was applied * error message is gone and there are only INFO message: old tuned version: ERROR tuned.utils.commands: Executing x86_energy_perf_policy error: WARNING tuned.plugins.plugin_cpu: your CPU doesn't support MSR_IA32_ENERGY_PERF_BIAS, ignoring CPU energy performance bias new tuned version: WARNING tuned.plugins.plugin_cpu: your CPU doesn't support MSR_IA32_ENERGY_PERF_BIAS, ignoring CPU energy performance bias -> VERIFIED
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0879