[libvirt] libvirt log format

Eric Blake eblake at redhat.com
Wed Jul 23 21:35:00 UTC 2014

On 07/23/2014 03:23 PM, Yuanzhen Gu wrote:
> Hello folks,
> Does any one know how to read the libvirt log information?
> For example,
> 2014-07-22 17:25:22.984+0000: 18571: debug : qemuMonitorIOProcess:356 :
> QEMU_MONITOR_IO_PROCESS: mon=0x7f733c000a40 buf={"timestamp": {"seconds":
> 1406049922, "microseconds": 983916}, "event": "STOP"}
> is there anyway to find the qemuMonitorIOProcess() function in the source
> code?  and what does "356" after that means?   Thanks!

I just answered your same question on the libvirt-users list; but in
short, 'git grep' is your friend, and 356 is the line number of the code
emitting the log message at the state of the source code used to build
the binary you are running.

Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 604 bytes
Desc: OpenPGP digital signature
URL: <http://listman.redhat.com/archives/libvir-list/attachments/20140723/5e3c09bd/attachment-0001.sig>

More information about the libvir-list mailing list