Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionLuiz Capitulino
2015-09-29 14:22:32 UTC
Created attachment 1078384[details]
lat.out that reproduces the issue
Description of problem:
We've been seeing that in some systems the files lapic_timer_adv_ns and lapic_timer_adv_ns.cpumodel are not being created in /usr/lib/tuned/realtime-virtual-host/.
I've debugged this issue down to find-lapictscdeadline-optimal.sh (silently) failing when run by tuned.
I'm attaching the lat.out file that reproduces the issue:
[root@virtlab401 realtime-virtual-host]# ./find-lapictscdeadline-optimal.sh /tmp/tmp.ZjZlVhDqe8/lat.out
optimal not found
[root@virtlab401 realtime-virtual-host]#
Btw, in those systems we ended up with 7000 written to /sys/module/kvm/parameters/lapic_timer_advance_ns, just because that's the last value tried by run-tscdeadline-latency.sh.
Version-Release number of selected component (if applicable): tuned-2.5.1-4.el7.noarch
How reproducible:
Steps to Reproduce:
1. Setup a KVM-RT host
2. The following files don't exist:
* /usr/lib/tuned/realtime-virtual-host/lapic_timer_adv_ns
* /usr/lib/tuned/realtime-virtual-host/lapic_timer_adv_ns.cpumodel
3. /sys/module/kvm/parameters/lapic_timer_advance_ns is 7000
Comment 1Jaroslav Škarvada
2015-10-02 10:11:47 UTC
Comment 7Jaroslav Škarvada
2015-11-16 17:32:07 UTC
(In reply to Jaroslav Škarvada from comment #1)
> Upstream commit:
> https://git.fedorahosted.org/cgit/tuned.git/commit/
> ?id=874762b4c06e3bc7862e119ee12a23a16352f649
>
Using this commit as the fix for this bugzilla.
> Also I am going to move:
> /usr/lib/tuned/realtime-virtual-host/lapic_timer_adv_ns
> /usr/lib/tuned/realtime-virtual-host/lapic_timer_adv_ns.cpumodel
>
> to /var/lib/tuned/...
>
> This is according to FHS and should also help with SELinux (if enabled).
>
Postponing this specific change to later 7.3 rebase.
Hi,
I'm confused from this bug and I don't know what is really expected result. What everything should be set and work? What all should I do for testing this bug?
# tuned-adm profile realtime-virtual-host
# ./find-lapictscdeadline-optimal.sh lat.out
./find-lapictscdeadline-optimal.sh: line 10: *100/ 3429: syntax error: operand expected (error token is "*100/ 3429")
optimal value for lapic_timer_advance_ns is: 7000
>> Optimal value seems well - 7000 - like in description.
>> There is syntax error, should I create a bug?
# cat /sys/module/kvm/parameters/lapic_timer_advance_ns
1000
>> Why there is 1000 and not 7000?
# ls /usr/lib/tuned/realtime-virtual-host
find-lapictscdeadline-optimal.sh lat.out run-tscdeadline-latency.sh script.sh tuned.conf
# ls /var/lib/tuned
ls: cannot access /var/lib/tuned: No such file or directory
>> Files lapic_timer_adv_ns and lapic_timer_adv_ns.cpumodel are missing in /usr/lib/tuned/realtime-virtual-host and /var/lib/tuned. Where is it? Are these files necessary?
# rpm -q tuned
tuned-2.7.1-2.el7.noarch
There is behavior on old tuned package:
# tuned-adm profile realtime-virtual-host
# ./find-lapictscdeadline-optimal.sh lat.out
optimal value for lapic_timer_advance_ns is: 6500
# cat /sys/module/kvm/parameters/lapic_timer_advance_ns
1000
# ls /usr/lib/tuned/realtime-virtual-host/
find-lapictscdeadline-optimal.sh lat.out run-tscdeadline-latency.sh script.sh tuned.conf
# ls /var/lib/tuned
ls: cannot access /var/lib/tuned: No such file or directory
# rpm -q tuned
tuned-2.5.1-4.el7_2.3.noarch
Is lat.out the one attached in this BZ? If it is, then I can't explain why it is working for you. But at the same time, this was a minor bug and I don't think it's worth it to spend time trying to figure out how an old version of tuned used to work.
In this case, I'd recommend skipping verification for this one.
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://rhn.redhat.com/errata/RHBA-2016-2479.html
Created attachment 1078384 [details] lat.out that reproduces the issue Description of problem: We've been seeing that in some systems the files lapic_timer_adv_ns and lapic_timer_adv_ns.cpumodel are not being created in /usr/lib/tuned/realtime-virtual-host/. I've debugged this issue down to find-lapictscdeadline-optimal.sh (silently) failing when run by tuned. I'm attaching the lat.out file that reproduces the issue: [root@virtlab401 realtime-virtual-host]# ./find-lapictscdeadline-optimal.sh /tmp/tmp.ZjZlVhDqe8/lat.out optimal not found [root@virtlab401 realtime-virtual-host]# Btw, in those systems we ended up with 7000 written to /sys/module/kvm/parameters/lapic_timer_advance_ns, just because that's the last value tried by run-tscdeadline-latency.sh. Version-Release number of selected component (if applicable): tuned-2.5.1-4.el7.noarch How reproducible: Steps to Reproduce: 1. Setup a KVM-RT host 2. The following files don't exist: * /usr/lib/tuned/realtime-virtual-host/lapic_timer_adv_ns * /usr/lib/tuned/realtime-virtual-host/lapic_timer_adv_ns.cpumodel 3. /sys/module/kvm/parameters/lapic_timer_advance_ns is 7000