Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Key systemtap-runtime parts such as /usr/bin/staprun and /usr/bin/stapio are now included in the Red Hat Enterprise Virtualization Hypervisor image to allow remote invocation of systemtap probing.
DescriptionFrank Ch. Eigler
2010-10-07 12:27:19 UTC
Please include key parts of systemtap-runtime in the RHEV-H image, to
permit remotely invoked systemtap probing. As of systemtap-1.3, these
parts would be:
/usr/bin/staprun
/usr/bin/stapio
By RHEL6.1, systemtap-1.4 should be available, and may include an
additional small binary to help smoothen the remote probing task.
The way this would work with current-day code is that a development/management
machine, with all the debuginfo / compilers goo installed, would have a stap
user run
stap -p4 FOO.stp
scp FOOBAR.ko root@rhev-host:FOOBAR.ko
ssh root@rhev-host staprun FOOBAR.ko
basically according to the 'cross-compilation' pattern of operation. There
is currently no man page that spells out this sequence, but is outlined on
our wiki:
http://sourceware.org/systemtap/wiki/TipCrossCompiling
With systemtap 1.4, these steps will be automated (with a proper man page
blurb).
Created attachment 476867[details]
Patch
Note: bug asks for /usr/bin/stapio, but rpm adds /usr/libexec/systemtap/stapio instead
Testing:
rpm -qa systemtap-runtime
ls /usr/bin/staprun
ls /usr/libexec/systemtap/stapio
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:
Key systemtap-runtime parts such as /usr/bin/staprun and /usr/bin/stapio are now included in the Red Hat Enterprise Virtualization Hypervisor image to allow remote invocation of systemtap probing.