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.
handle_qmp_command was part of the functionality required by the flight recorder. I have sent the following patch upstream:
[PATCH 0/2] monitor: add trace events for HMP and QMP commands
Once it has been merged I will backport it and the flight recorder will work again.
(In reply to Stefan Hajnoczi from comment #2)
> handle_qmp_command was part of the functionality required by the flight
> recorder. I have sent the following patch upstream:
> [PATCH 0/2] monitor: add trace events for HMP and QMP commands
>
> Once it has been merged I will backport it and the flight recorder will work
> again.
You've set it to POST, but I don't see the backport yet, reverting back to ASSIGNED.
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://access.redhat.com/errata/RHSA-2017:2392
Description of problem: compling qemu-kvm failed when executed "service systemtap start qemu_kvm" Version-Release number of selected component (if applicable): [root@localhost rhel]# rpm -qa |grep kernel-devel kernel-devel-3.10.0-675.el7.x86_64 [root@localhost rhel]# uname -r 3.10.0-675.el7.x86_64 [root@localhost rhel]# rpm -qa |grep qemu-kvm-rhev qemu-kvm-rhev-2.9.0-7.el7.x86_64 How reproducible: 3/3 Steps to Reproduce: 1. cp /usr/share/qemu-kvm/systemtap/script.d/qemu_kvm.stp /etc/systemtap/script.d/ 2. cp /usr/share/qemu-kvm/systemtap/conf.d/qemu_kvm.conf /etc/systemtap/conf.d/ Actual results: [root@localhost script.d]# service systemtap start qemu_kvm Starting systemtap: Compiling qemu_kvm ... error [FAILED] Expected results: complied success Additional info: [root@localhost script.d]# cat /etc/systemtap/script.d/qemu_kvm.stp probe qemu.kvm.simpletrace.handle_qmp_command,qemu.kvm.simpletrace.monitor_protocol_*,qemu.kvm.simpletrace.migrate_set_state {} [root@localhost script.d]# cat /etc/systemtap/conf.d/qemu_kvm.conf # Force load uprobes (see BZ#1118352) stap -e 'probe process("/usr/libexec/qemu-kvm").function("main") { printf("") }' -c true qemu_kvm_OPT="-s4" # per-CPU buffer size, in megabytes PS: compile successfully when deleted qemu.kvm.simpletrace.handle_qmp_command [root@localhost script.d]# cat qemu_kvm.stp probe qemu.kvm.simpletrace.monitor_protocol_*,qemu.kvm.simpletrace.migrate_set_state {}