Bug 1516220

Summary: -trace help prints an incomplete list of trace events
Product: Red Hat Enterprise Linux Advanced Virtualization Reporter: Stefan Hajnoczi <stefanha>
Component: qemu-kvmAssignee: Philippe Mathieu-Daudé <philmd>
Status: CLOSED ERRATA QA Contact: jingzhao <jinzhao>
Severity: low Docs Contact:
Priority: medium    
Version: ---CC: chayang, ddepaula, jinzhao, juzhang, kanderso, knoel, mtessun, philmd, rbalakri, thuth, virt-maint
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: qemu-kvm-4.1.0-7.module+el8.1.0+4177+896cb282 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-06 07:10:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Stefan Hajnoczi 2017-11-22 10:04:23 UTC 
Description of problem:

"qemu-system-x86_64 -trace help" prints an incomplete list of trace events.  The SystemTap .stp tapset file includes additional trace events that are not listed by QEMU.

The reason for this bug is that QEMU's -trace, "info trace-events", and tracing monitor commands are ineffective when SystemTap is used.  SystemTap lists and enables/disables trace events through a different mechanism than QEMU.

Therefore QEMU's view of trace events is incomplete when SystemTap is used.  It would be better to let the user know to use SystemTap instead of display incomplete information.

How reproducible:

100%

Steps to Reproduce:

1. Compare "qemu-system-x86_64 -trace help" output against /usr/share/systemtap/tapset/qemu-system-x86_64.stp

Actual results:

QEMU displays a short, incomplete list of trace events.

Expected results:

QEMU either displays the full list or prompts the user to use SystemTap directly.
Comment 5 Danilo de Paula 2019-09-04 14:10:03 UTC 
We need QA_ACK, please.
Comment 12 errata-xmlrpc 2019-11-06 07:10:39 UTC 
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/RHBA-2019:3723