The DEBUG log level is very verbose and can quickly fill a filesystem hosting /var/log/libvirt/libxl/
Signed-off-by: Jim Fehlig <[email protected]> --- Ideally, the log level should match what is configured in libvirtd.conf. Are the logging knob settings available in the drivers? If not, this would be a good option for a future /etc/libvirt/libxl.conf. src/libxl/libxl_conf.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/libxl/libxl_conf.c b/src/libxl/libxl_conf.c index e092b11..34dbfe4 100644 --- a/src/libxl/libxl_conf.c +++ b/src/libxl/libxl_conf.c @@ -1350,7 +1350,7 @@ libxlDriverConfigNew(void) cfg->logger = (xentoollog_logger *)xtl_createlogger_stdiostream(cfg->logger_file, - XTL_DEBUG, 0); + XTL_ERROR, 0); if (!cfg->logger) { VIR_ERROR(_("cannot create logger for libxenlight, disabling driver")); goto error; -- 1.8.4.5 -- libvir-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/libvir-list
