Bug 2513629
| Summary: | tuned-adm verify always fails | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Petr Sklenar <psklenar> | ||||
| Component: | tuned | Assignee: | Jaroslav Škarvada <jskarvad> | ||||
| Status: | NEW --- | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 45 | CC: | jskarvad, pzacik | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | --- | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | Type: | --- | |||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Petr Sklenar
2026-08-10 19:38:57 UTC
Created attachment 2154177 [details]
tuned.log from Raspberry Pi 400 - shows boost write failures and verify errors
Confirmed also on x86_64 KVM virtual machine (F45 Rawhide): Host CPU: Intel Core Ultra 7 165H Guest: QEMU/KVM, 8 vCPUs Kernel: 7.2.0-0.rc6.260806g0d8395707651.51.fc45.x86_64 tuned-2.27.0-3.fc45.noarch All 3 profiles fail verify due to boost: - balanced (active): boost='None', expected '1' on all 8 CPUs - virtual-guest (recommended): same boost failure - throughput-performance: same KVM guests have no cpufreq boost support - /sys/devices/system/cpu/cpufreq/policy0/boost does not exist. Additional failures on x86_64 VM not seen on RPi: - ALPM: 6 SCSI hosts report max_performance instead of med_power_with_dipm - cpufreq_conservative module not loaded (balanced profile expects it) This bug affects both aarch64 (RPi 400) and x86_64 (KVM guests) - any platform where CPU boost is not available. This bug appears to have been reported against 'rawhide' during the Fedora Linux 45 development cycle. Changing version to 45. root@fedora:~# tuned-adm verify
Verification failed, current system settings differ from the preset profile.
You can mostly fix this by restarting the TuneD daemon, e.g.:
systemctl restart tuned
or
service tuned restart
Sometimes (if some plugins like bootloader are used) a reboot may be required.
See TuneD log file ('/var/log/tuned/tuned.log') for details.
root@fedora:~# head /var/log/tuned/tuned.log
2026-10-22 13:05:22,696 INFO tuned.daemon.application: TuneD: 2.28.0, kernel: 7.2.11-300.fc45.x86_64
2026-10-22 13:05:22,696 INFO tuned.daemon.application: dynamic tuning is globally disabled
2026-10-22 13:05:22,700 INFO tuned.daemon.daemon: using sleep interval of 1 second(s)
2026-10-22 13:05:22,701 INFO tuned.daemon.daemon: Running in automatic mode, checking what profile is recommended for your configuration.
2026-10-22 13:05:22,841 INFO tuned.daemon.daemon: Using 'virtual-guest' profile
2026-10-22 13:05:22,842 INFO tuned.profiles.loader: loading profile: virtual-guest
2026-10-22 13:05:22,844 INFO tuned.daemon.controller: starting controller
2026-10-22 13:05:22,844 INFO tuned.daemon.daemon: starting tuning
2026-10-22 13:05:22,850 INFO tuned.plugins.base: instance cpu: assigning devices cpu4, cpu3, cpu2, cpu0, cpu1, cpu5, cpu7, cpu6
2026-10-22 13:05:22,850 INFO tuned.plugins.plugin_cpu: We are running on an x86 GenuineIntel platform
---
still issue with f45 rc compose
tuned-2.28.0-1.fc45.noarch
We need to address it in the CPU plugin. In the meantime verification with the 'tuned-adm verify -i' should work. TuneD 2.28 has the fix applied. Could you provide the related TuneD log bits with the tuned-2.28? From comment 4 it isn't clear what's failing there. root@fedora:~# systemctl restart tuned
root@fedora:~# tuned-adm verify
Verification failed, current system settings differ from the preset profile.
You can mostly fix this by restarting the TuneD daemon, e.g.:
systemctl restart tuned
or
service tuned restart
Sometimes (if some plugins like bootloader are used) a reboot may be required.
See TuneD log file ('/var/log/tuned/tuned.log') for details.
root@fedora:~# tuned-adm verify -i
Verification failed, current system settings differ from the preset profile.
You can mostly fix this by restarting the TuneD daemon, e.g.:
systemctl restart tuned
or
service tuned restart
Sometimes (if some plugins like bootloader are used) a reboot may be required.
See TuneD log file ('/var/log/tuned/tuned.log') for details.
---------------
VM, KDE, https://kojipkgs.fedoraproject.org/compose/45/Fedora-45-20261028.1/compose/KDE/x86_64/iso/
-----------------
LOGS
/var/log/tuned/tuned.log: https://psklenar.fedorapeople.org/mypaste/tuned.log
journalct: https://psklenar.fedorapeople.org/mypaste/journalctl
root@fedora:~# rpm -q tuned tuned-2.28.0-1.fc45.noarch https://psklenar.fedorapeople.org/mypaste/journalctl1 is the correct journalctl, please ignore previous one tuned-adm verify
==> /var/log/tuned/tuned.log <==
2026-10-29 20:59:50,967 INFO tuned.daemon.daemon: verifying profile(s): balanced
2026-10-29 20:59:50,968 ERROR tuned.plugins.plugin_modules: verify: failed: 'module 'cpufreq_conservative' is not loaded'
2026-10-29 20:59:50,969 INFO tuned.plugins.base: verify: passed: device snd_hda_intel: 'timeout' = '10'
2026-10-29 20:59:50,969 INFO tuned.plugins.base: verify: passed: device snd_hda_intel: 'reset_controller' = '1'
2026-10-29 20:59:50,969 ERROR tuned.plugins.base: verify: failed: device host0: 'alpm' = 'max_performance', expected 'med_power_with_dipm'
2026-10-29 20:59:50,970 ERROR tuned.plugins.base: verify: failed: device host4: 'alpm' = 'max_performance', expected 'med_power_with_dipm'
2026-10-29 20:59:50,970 ERROR tuned.plugins.base: verify: failed: device host5: 'alpm' = 'max_performance', expected 'med_power_with_dipm'
2026-10-29 20:59:50,970 ERROR tuned.plugins.base: verify: failed: device host6: 'alpm' = 'None', expected 'med_power_with_dipm'
2026-10-29 20:59:50,970 ERROR tuned.plugins.base: verify: failed: device host2: 'alpm' = 'max_performance', expected 'med_power_with_dipm'
2026-10-29 20:59:50,970 ERROR tuned.plugins.base: verify: failed: device host1: 'alpm' = 'max_performance', expected 'med_power_with_dipm'
2026-10-29 20:59:50,971 ERROR tuned.plugins.base: verify: failed: device host3: 'alpm' = 'max_performance', expected 'med_power_with_dipm'
2026-10-29 20:59:50,971 ERROR tuned.plugins.base: verify: failed: device cpu6: 'boost' = 'None', expected '1'
2026-10-29 20:59:50,971 ERROR tuned.plugins.base: verify: failed: device cpu0: 'boost' = 'None', expected '1'
2026-10-29 20:59:50,972 ERROR tuned.plugins.base: verify: failed: device cpu4: 'boost' = 'None', expected '1'
2026-10-29 20:59:50,972 ERROR tuned.plugins.base: verify: failed: device cpu7: 'boost' = 'None', expected '1'
2026-10-29 20:59:50,972 ERROR tuned.plugins.base: verify: failed: device cpu2: 'boost' = 'None', expected '1'
2026-10-29 20:59:50,972 ERROR tuned.plugins.base: verify: failed: device cpu1: 'boost' = 'None', expected '1'
2026-10-29 20:59:50,972 ERROR tuned.plugins.base: verify: failed: device cpu3: 'boost' = 'None', expected '1'
2026-10-29 20:59:50,972 ERROR tuned.plugins.base: verify: failed: device cpu5: 'boost' = 'None', expected '1'
Verification failed, current system settings differ from the preset profile.
You can mostly fix this by restarting the TuneD daemon, e.g.:
systemctl restart tuned
or
service tuned restart
Sometimes (if some plugins like bootloader are used) a reboot may be required.
See TuneD log file ('/var/log/tuned/tuned.log') for details.
root@fedora:~# ls /sys/devices/system/cpu/cpufreq/ -la total 0 drwxr-xr-x. 2 root root 0 Oct 29 21:03 . drwxr-xr-x. 17 root root 0 Oct 29 18:54 .. ###nothing here |