[libvirt] Reporting log/error messages through capabilities

Kashyap Chamarthy kchamart at redhat.com
Wed Feb 19 13:23:15 UTC 2014


On Tue, Feb 18, 2014 at 11:11:10PM +0000, Richard W.M. Jones wrote:

[. . .]

> Are there other unanticipated problems here?  I think one is that
> libvirt doesn't appear to collect detailed log information by default,
> (unless the user edits log_level).  That's assuming I understand the
> code correctly.  Personally I think libvirt should always collect
> debug information, 

Interestingly, recently there was a similar debate[1] in OpenStack
upstream and RDO lands. A CI fix landed to enable libvirt debug logs on
OpenStack Jenkins machines, after a discussion on the list, it got
reverted, and settled on using these filters, per Dan's suggestion:

      log_filters="1:libvirt 1:qemu 1:conf 1:security 3:event 3:json 3:file 1:util"
      log_outputs="1:file:/var/log/libvirt/libvirtd.log"


 [1] https://bugzilla.redhat.com/show_bug.cgi?id=1061753


-- 
/kashyap




More information about the libvir-list mailing list