...
Description of problem: When RHEL 8.6 is installed and then the RT kernel is installed using the yum method, the kernel-rt-kvm RPM is not installed by default. See: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_for_real_time/8/html-single/installing_rhel_8_for_real_time/index#proc_installing-red-hat-enterprise-linux-for-real-time-using-yum_assembly_installing-rhel-for-real-time If tuned is then used to apply the cpu-partitioning profile, there is a silent failure with the following errors (in /var/log/tuned/tuned.log): 2022-12-15 11:13:30,086 INFO tuned.plugins.plugin_script: calling script '/usr/lib/tuned/cpu-partitioning/script.sh' with arguments '['start']' 2022-12-15 11:13:30,132 ERROR tuned.plugins.plugin_script: script '/usr/lib/tuned/cpu-partitioning/script.sh' error output: 'modinfo: ERROR: Module kvm not found. modinfo: ERROR: Module kvm not found. modinfo: ERROR: Module kvm_intel not found.' Note that this is a silent failure - it looks like the tuned profile was applied successfully, but the /usr/lib/tuned/cpu-partitioning/script.sh exits early and doesn't complete. Version-Release number of selected component (if applicable): tuned-profiles-cpu-partitioning-2.19.0-1.1.20221013git12fa4d58.el8fdp.noarch How reproducible: Always Steps to Reproduce: 1. Install RHEL 8.6 2. Install RT kernel 3. Apply tuned cpu-partitioning profile Actual results: The cpu-partitioning profile is not applied properly. The only indication of failure is in the tuned logs. Expected results: The cpu-partitioning profile is applied properly. Additional info: The workaround is to enable the rhel-8-for-x86_64-nfv-rpms repo and install the kernel-rt-kvm RPM. I'm not sure if that would be available to all users? Also, I don't think this happened in RHEL 8.5 (but I'm not 100% sure about that).
Done
Click on a version to see all relevant bugs
Red Hat Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.