From ae7b4f9b9e811f2c0abfb4f7f4e85dd91ca1c2b3 Mon Sep 17 00:00:00 2001 From: Kashyap Chamarthy Date: Tue, 31 Mar 2015 20:49:15 +0200 Subject: [PATCH] functions-libvirt: Enable 'qemu_monitor' logging filter for libvirt A lot of libvirt interactions with QEMU are via the QEMU monitor console, which allows you to either query or modify the state of a virtual machine. Spefici examples include: querying the status of live block operations, live snapshot operations, live migration, etc. Enabling the 'qemu_monitor' log filter allows us to capture precisely what commands libvirt is sending to QEMU. Note that the log level was intentionally set to '1' (i.e. debug) for this specific filter, because (a) it's not extremely verbose, (b) when something breaks, it's helpful to have the exact sequence of interactions between libvirt and QEMU. Change-Id: Iba95b6bd7c9f197c8d48c7d978f538e50d4e31fa --- lib/nova_plugins/functions-libvirt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lib/nova_plugins/functions-libvirt b/lib/nova_plugins/functions-libvirt index edcf73ebe2..05ef605b04 100644 --- a/lib/nova_plugins/functions-libvirt +++ b/lib/nova_plugins/functions-libvirt @@ -99,9 +99,9 @@ EOF # source file paths, not relative paths. This screws with the matching # of '1:libvirt' making everything turn on. So use libvirt.c for now. # This will have to be re-visited when Ubuntu ships libvirt >= 1.2.3 - local log_filters="1:libvirt.c 1:qemu 1:conf 1:security 3:object 3:event 3:json 3:file 1:util" + local log_filters="1:libvirt.c 1:qemu 1:conf 1:security 3:object 3:event 3:json 3:file 1:util 1:qemu_monitor" else - local log_filters="1:libvirt 1:qemu 1:conf 1:security 3:object 3:event 3:json 3:file 1:util" + local log_filters="1:libvirt 1:qemu 1:conf 1:security 3:object 3:event 3:json 3:file 1:util 1:qemu_monitor" fi local log_outputs="1:file:/var/log/libvirt/libvirtd.log" if ! grep -q "log_filters=\"$log_filters\"" /etc/libvirt/libvirtd.conf; then