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.
Verified with kernel-rt-3.10.0-957.48.1.rt56.966.el7.x86_64:
1. Default value of nx_huge_pages is N. This is expected.
# systool -vm kvm | grep nx_huge
nx_huge_pages_recovery_ratio= "0"
nx_huge_pages = "N"
2. With mitigations off, 24h cyclictest max latency is 41us. We expect 20us, but I don't think the spike is caused by this bug, and Bug 1790469 is tracking it.
==Results==
(1)Single VM with 1 rt vCPU:
# Min Latencies: 00005
# Avg Latencies: 00006
# Max Latencies: 00020
(2)Single VM with 8 rt vCPUs:
# Min Latencies: 00005 00005 00005 00005 00005 00005 00005 00005
# Avg Latencies: 00006 00005 00005 00005 00005 00005 00005 00005
# Max Latencies: 00020 00017 00016 00017 00016 00021 00016 00016
(3)Multiple VMs each with 1 rt vCPU:
- VM1
# Min Latencies: 00005
# Avg Latencies: 00006
# Max Latencies: 00030
- VM2
# Min Latencies: 00005
# Avg Latencies: 00006
# Max Latencies: 00021
- VM3
# Min Latencies: 00005
# Avg Latencies: 00006
# Max Latencies: 00020
- VM4
# Min Latencies: 00005
# Avg Latencies: 00007
# Max Latencies: 00041
So this bug has been fixed. Move to 'VERIFIED'.