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-01-05 14:47:11 UTC
Description of problem:
For real-time, we need to be able to disable the PMU. This is done by passing pmu=off to QEMU, like:
-cpu host,pmu=off
However, libvirt doesn't know the "pmu=off" flag.
Version-Release number of selected component (if applicable): libvirt-1.2.8-11.el7.x86_64
Comment 1Martin Kletzander
2015-01-05 15:50:33 UTC
Do all QEMU versions support this flag or only some of them? If the latter is true, how can we get that support information from QMP? We need that in order to error out properly before even starting QEMU.
(In reply to Martin Kletzander from comment #1)
> Do all QEMU versions support this flag or only some of them? If the latter
> is true, how can we get that support information from QMP? We need that in
> order to error out properly before even starting QEMU.
I believe there's no way to query for the availability of the "pmu" property yet, because we still don't have working CPU class introspection in QEMU. This should be implemented as part of bug 824987.
Comment 5Martin Kletzander
2015-01-19 07:49:46 UTC
Fixed upstream by commits v1.2.11-190-g1993901 and v1.2.11-191-g6514c04:
commit 199390117c9ad010c2cc84a152943a5f006ec2b1
Author: Martin Kletzander <mkletzan>
Date: Mon Jan 5 16:21:51 2015 +0100
docs, schema, conf: Add support for PMU feature
commit 6514c04c182f0c59ce8d491c37f0dc4b73703311
Author: Martin Kletzander <mkletzan>
Date: Mon Jan 5 16:52:18 2015 +0100
qemu: Add support for enabling/disabling PMU
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-2015-2202.html