Bug 698469

Comment 11 from related bz

(In reply to comment #10)
> (In reply to comment #9)
> > Is it possible to get systemtap in the RHEVH 5.x as well?
> 
> Cloned as bug 698469.  Up to PM as to whether it gets in or not.

Not sure about that, RHEL-5 has systemtap 1.3
Frank, is that good enough?

And BTW:
> With systemtap 1.4, these steps will be automated (with a proper man page
> blurb).

which manpage is that?

Comment 12 from related bz


systemtap 1.3 should also be workable for a rhel5 rhevm build, but would need
the manual remote-invocation steps in comment #4.  (A shortly arriving new
version of systemtap, installed on the development machine only, should bring
automation, even with an older systemtap-runtime.)

> And BTW:
> > With systemtap 1.4, these steps will be automated (with a proper man page
> > blurb).
> which manpage is that?

That'd be the stap(1) man page, not part of the runtime.

Created attachment 498020 [details]
Patch

"Not sure about that, RHEL-5 has systemtap 1.3  Frank, is that good enough?"

Good enough, yes.  

Ideally rhev-h should be kept up-to-date with respect to the underlying
rhel systemtap spins on an ongoing basis.  We're shipping stap1.4 for rhel6.1
and stap1.3 for rhel5.7.  We're anticipating stap1.5 for rhel6.2 and rhel5.8,
which will bring more remote-operation improvements.

(In reply to comment #3)
> "Not sure about that, RHEL-5 has systemtap 1.3  Frank, is that good enough?"
> 
> Good enough, yes.  
> 
> Ideally rhev-h should be kept up-to-date with respect to the underlying
> rhel systemtap spins on an ongoing basis.  We're shipping stap1.4 for rhel6.1
> and stap1.3 for rhel5.7.  We're anticipating stap1.5 for rhel6.2 and rhel5.8,
> which will bring more remote-operation improvements.

rhev-h will automatically pick up whichever version is shipped in a release.  So in 5.7, we'll get 1.3.  This is assuming we're not shipping multiple versions, i.e. systemtap-runtime is 1.3 and also shipping systemtap-runtime1.4 alongside.

Verified on rhev-hypervisor-5.7-20110622.0.el5, systemtap-runtime is included:
# rpm -ql systemtap-runtime-1.3-8.el5
/usr/bin/stap-authorize-signing-cert
/usr/bin/stap-report
/usr/bin/staprun
/usr/lib64/systemtap/staplog.so
/usr/libexec/systemtap/stap-authorize-cert
/usr/libexec/systemtap/stap-env
/usr/libexec/systemtap/stapio
/usr/share/doc/systemtap-runtime-1.3
/usr/share/doc/systemtap-runtime-1.3/AUTHORS
/usr/share/doc/systemtap-runtime-1.3/COPYING
/usr/share/doc/systemtap-runtime-1.3/NEWS
/usr/share/doc/systemtap-runtime-1.3/README
/usr/share/man/man7/stappaths.7.gz
/usr/share/man/man8/stap-authorize-signing-cert.8.gz
/usr/share/man/man8/staprun.8.gz

    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/libexec/systemtap/stapio are now included in the Red Hat Enterprise Virtualization Hypervisor image to allow remote invocation of systemtap probing.

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-1090.html