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
This commit is contained in:
parent
206c596d69
commit
ae7b4f9b9e
@ -99,9 +99,9 @@ EOF
|
|||||||
# source file paths, not relative paths. This screws with the matching
|
# source file paths, not relative paths. This screws with the matching
|
||||||
# of '1:libvirt' making everything turn on. So use libvirt.c for now.
|
# 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
|
# 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
|
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
|
fi
|
||||||
local log_outputs="1:file:/var/log/libvirt/libvirtd.log"
|
local log_outputs="1:file:/var/log/libvirt/libvirtd.log"
|
||||||
if ! grep -q "log_filters=\"$log_filters\"" /etc/libvirt/libvirtd.conf; then
|
if ! grep -q "log_filters=\"$log_filters\"" /etc/libvirt/libvirtd.conf; then
|
||||||
|
Loading…
Reference in New Issue
Block a user