Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1516220 - -trace help prints an incomplete list of trace events
Summary: -trace help prints an incomplete list of trace events
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux Advanced Virtualization
Classification: Red Hat
Component: qemu-kvm
Version: ---
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: rc
: ---
Assignee: Stefan Hajnoczi
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-22 10:04 UTC by Stefan Hajnoczi
Modified: 2019-02-22 22:10 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.