qemu does not generate a qemu-kvm.stp tapset file

[William Cohen]

To make the systemtap probing easier to use qemu generates qemu*.stp files with aliases for various events for each of the executables. The installer places these files in /usr/share/systemtap/tapset/. These files are generated by the tracetool. However, the /usr/bin/qemu-kvm is produced with a copy:

 cp -a x86_64-softmmu/qemu-system-x86_64 qemu-kvm

No matching qemu-kvm.stp generated for the qemu-kvm executable. It would be really nice if that tapset file is generated so people can use more symbolic probe points.

[Stefan Hajnoczi (stefanha)]

On Tue, Sep 13, 2011 at 5:08 AM, William Cohen
<email address hidden> wrote:
> Public bug reported:
>
> To make the systemtap probing easier to use qemu generates qemu*.stp
> files with aliases for various events for each of the executables. The
> installer places these files in /usr/share/systemtap/tapset/.  These
> files are generated by the tracetool. However, the /usr/bin/qemu-kvm is
> produced with a copy:
>
>  cp -a x86_64-softmmu/qemu-system-x86_64 qemu-kvm
>
> No matching qemu-kvm.stp generated for the qemu-kvm executable. It would
> be really nice if that tapset file is generated so people can use more
> symbolic probe points.

Jes Sorensen added an option to make this possible:

http://repo.or.cz/w/qemu.git/commitdiff/e323c93edf3abb67c37b8e08b78da4835880f12e

Distro packaging scripts can make use of this tracetool option to
generate .stp files for qemu-kvm in its install path.

I think you need to file a bug with your distro.

Stefan

[William Cohen (wcohen)]

You are correct. the qemu.spec file is doing the copy.