Bug 1144325
| Summary: | Can not probe "qemu.kvm.virtio_blk_data_plane_complete_request" | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | langfang <flang> |
| Component: | qemu-kvm-rhev | Assignee: | Stefan Hajnoczi <stefanha> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.1 | CC: | flang, hhuang, juzhang, qiguo, qzhang, sluo, virt-maint, xfu |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | qemu-kvm-rhev-2.1.2-5.el7 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-03-05 09:55:51 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: | |||
Thanks. That trace event no longer exists in RHEL or upstream. I will send a patch to drop it upstream and backport it. Patches sent to rhvirt-patches Fix included in qemu-kvm-rhev-2.1.2-5.el7 Test on latest version:
Host:
# uname -r
3.10.0-191.el7.x86_64
# rpm -q qemu-kvm-rhev
qemu-kvm-rhev-2.1.2-5.el7.x86_64
Steps
1.Install kernel-debuginfo and systemtap package on host
2.On host:
#vim /usr/share/systemtap/tapset/qemu-kvm.stp
...
not found the event of "virtio_blk_data_plane_complete_request"
3.Create script on host
# cat virtio_blk_data_plane_complete_request.stp
probe qemu.kvm.virtio_blk_data_plane_complete_request
{
printf("s=%d\n",s);
printf("head=%d\n",head);
printf("ret=%d\n",ret);
}
4.Execute virtio_blk_data_plane_complete_request.stp
#stap virtio_blk_data_plane_complete_request.stp
After step4:
# stap virtio_blk_data_plane_complete_request.stp
semantic error: while resolving probe point: identifier 'qemu' at virtio_blk_data_plane_complete_request.stp:1:7
source: probe qemu.kvm.virtio_blk_data_plane_complete_request
^
semantic error: probe point mismatch (similar: virtio_blk_data_plane_process_request, pvscsi_complete_request, virtio_blk_data_plane_start, virtio_blk_data_plane_stop, virtio_blk_req_complete): identifier 'virtio_blk_data_plane_complete_request' at :1:16
source: probe qemu.kvm.virtio_blk_data_plane_complete_request
^
Pass 2: analysis failed. [man error::pass2]
According to above test and comment2, this bug has been fixed.
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://rhn.redhat.com/errata/RHSA-2015-0624.html |
Description of problem: Can not probe "qemu.kvm.virtio_blk_data_plane_complete_request" Version-Release number of selected component (if applicable): Host: # uname -r 3.10.0-144.el7.x86_64 # rpm -q qemu-kvm-rhev qemu-kvm-rhev-2.1.0-4.el7.x86_64 guest:rhel7 How reproducible: 100% Steps to Reproduce: 1.Install kernel-debuginfo and systemtap package on host 2.On host: #vim /usr/share/systemtap/tapset/qemu-kvm.stp ... probe qemu.kvm.virtio_blk_data_plane_complete_request = process("/usr/libexec/qemu-kvm").mark("virtio_blk_data_plane_complete_request") { s = $arg1; head = $arg2; ret = $arg3; } .... 3.Create script on host # cat virtio_blk_data_plane_complete_request.stp probe qemu.kvm.virtio_blk_data_plane_complete_request { printf("s=%d\n",s); printf("head=%d\n",head); printf("ret=%d\n",ret); } 4.Execute virtio_blk_data_plane_complete_request.stp #stap virtio_blk_data_plane_complete_request.stp Results: # stap virtio_blk_data_plane_complete_request.stp semantic error: while resolving probe point: identifier 'process' at /usr/share/systemtap/tapset/qemu-kvm.stp:408:57 source: probe qemu.kvm.virtio_blk_data_plane_complete_request = process("/usr/libexec/qemu-kvm").mark("virtio_blk_data_plane_complete_request") ^ semantic error: no match (similar marks: virtio_blk_data_plane_process_request, virtio_blk_data_plane_start, virtio_blk_data_plane_stop, virtio_blk_req_complete, virtio_blk_rw_complete) semantic error: while resolving probe point: identifier 'qemu' at virtio_blk_data_plane_complete_request.stp:1:7 source: probe qemu.kvm.virtio_blk_data_plane_complete_request ^ semantic error: no match Pass 2: analysis failed. [man error::pass2] Actual results: Should work well Expected results: Additional info: