On Thu, Oct 21, 2010 at 09:59:55PM +0200, Daniel Veillard wrote:
On Thu, Oct 21, 2010 at 07:19:32PM +0100, Daniel P. Berrange wrote:
> Adds initial support for dtrace static probes in libvirtd
> daemon, assuming use of systemtap dtrace compat shim on
> Linux. The probes are inserted for network client connect,
> disconnect, TLS handshake states and authentication protocol
> states.
>
> This can be tested by running the xample program and then
> attempting to connect with any libvirt client (virsh,
> virt-manager, etc).
>
> # stap examples/systemtap/client.stp
> Client fd=44 connected readonly=0
> Client fd=44 auth polkit deny pid:24997,uid:500
> Client fd=44 disconnected
> Client fd=46 connected readonly=1
> Client fd=46 auth sasl allow test
> Client fd=46 disconnected
>
> For unknown reasons, libvirtd must be restarted after
> the stap script is launched, otherwise the probes are
> not enabled. This bug needs to be fixed, probably in
> systemtap itself, to allow probing an existing running
> daemon.
Wasn't that problem found ? I though so ...
Yes it is partially solved, I'll remove this comment since
it isn't really relevant to the changeset.
Daniel
--
|: Red Hat, Engineering, London -o-
http://people.redhat.com/berrange/ :|
|:
http://libvirt.org -o-
http://virt-manager.org -o-
http://deltacloud.org :|
|:
http://autobuild.org -o-
http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|