[libvirt] [PATCH] 0/8 logging infrastructure for libvirt[d]

Daniel P. Berrange berrange at redhat.com
Wed Dec 17 15:57:37 UTC 2008

On Wed, Dec 17, 2008 at 04:06:38PM +0100, Daniel Veillard wrote:
>   In practice
>    export LIBVIRT_DEBUG=1
>    export LIBVIRT_LOG_OUTPUTS="0:file:virsh.log"
> and then running virsh will accumulate all logging to the virsh.log
> file in the current directory.

This looks great. 

>   One thing which I feel is somewhat incomplete is that it's impossible
> to remotely get debugging output from the libvirt daemon serving the
> requests. Currently all logs are also accumulated in a cyclic logging
> buffer, I would associate a dump function later to be hooked for example
> to a signal handler in the daemon. But I'm unsure we should allow
> dumping logging information to the remote end, probably not the whole
> set.

I've been wondering whether we should create an explicit tool for
admin of the libvirtd daemon itself. Basically something for querying
state, and performing operations wrt to the daemon for things outside
the scope of the libvirt API. For example, something to get details of
active client connections, and forceably drop a client. Being able to
have an API to configure the log level / setup of the dameon would be
a useful thing. We can easily layer this kind of thing in as another
RPC protocol in parallel with the existing protocol, and have simple
CLI tool libvirtd-admin.  SQUID has a 'squidclient' tool and a CGI
script for administration of the server itself.

|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

More information about the libvir-list mailing list