Red Hat Bugzilla – Bug 672441
Tracetool autogenerate qemu-kvm.stp with wrong qemu-kvm path
Last modified: 2013-01-09 18:31:03 EST
Description of problem: I saw tracetool regards the path of qemu-kvm as /usr/bin instead of /usr/libexec in /usr/share/systemtap/tapset/qemu-kvm.stp When I exec stp script call the tracepoint ,there is no output eg: probe qemu.kvm.qemu_memalign { printf("qemu_memalign alignment=%d ,size=%d ,ptr=%p\n",alignment,size,ptr) } we need to change it to the right path. Version-Release number of selected component (if applicable): qemu-kvm-0.12.1.2-2.131.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1.cat qemu-kvm.stp |grep probe Actual results: probe qemu.kvm.qemu_malloc = process("/usr/bin/qemu-kvm").mark("qemu_malloc") probe qemu.kvm.qemu_realloc = process("/usr/bin/qemu-kvm").mark("qemu_realloc") probe qemu.kvm.qemu_free = process("/usr/bin/qemu-kvm").mark("qemu_free") ..... Expected results: all the /usr/bin/qemu-kvm should change to /usr/libexec/qemu-kvm eg. probe qemu.kvm.qemu_malloc = process("/usr/libexec/qemu-kvm").mark("qemu_malloc") probe qemu.kvm.qemu_realloc = process("/usr/libexec/qemu-kvm").mark("qemu_realloc") probe qemu.kvm.qemu_free = process("/usr/libexec/qemu-kvm").mark("qemu_free" Additional info:
Tried on qemu-kvm-0.12.1.2-2.144.el6 Path changed to /usr/libexec/qemu-kvm in qemu-kvm.stp. bcao--->jes # cat /usr/share/systemtap/tapset/qemu-kvm.stp|grep probe probe qemu.system.x86_64.qemu_malloc probe qemu.system.x86_64.qemu_realloc .... Why use "qemu.system.x86_64.XXX" instead of "probe qemu.kvm.XXXX" ? Is it made by design or a regression ? Mike
This is an additional bug related to the fix I posted with the patches here. I should have caught it when I posted the initial patch, but I only looked at the path :( I'll look into fixing this.
Verified on qemu-kvm-0.12.1.2-2.147.el6 Repeat the steps in comment #0. Actual Results: Path changed to /usr/libexec/qemu-kvm in qemu-kvm.stp. "qemu.kvm.XXX" was used instead of "qemu.system.x86_64.XXX" Based on above ,this issue has been fixed.
move to verified based on comment#9
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: This is a fix to a problem introduced in an interim RHEL6.1 patch backport. It is not a regression from 6.0 and not customer exposed.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2011-0534.html