I was debugging a case where 200 snapshots of a disk would result in a
VERY long reconnect time after libvirtd restart when debug logging was
enabled.

I've figured out that qemu responds with 9MiB of json after calling
"query-named-block-nodes" and this resulted in > 26 GiB of libvirtd
debug log just to process the message.

I'll report the qemu flaw separately.

Peter Krempa (2):
  util: probe: Add quiet versions of the "PROBE" macro
  qemu: monitor: Decrease logging verbosity

 src/qemu/qemu_monitor.c      | 4 ++--
 src/qemu/qemu_monitor_json.c | 3 +++
 src/util/virprobe.h          | 8 ++++++++
 3 files changed, 13 insertions(+), 2 deletions(-)

-- 
2.15.0

--
libvir-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/libvir-list

Reply via email to