File ba25c214-libxl-log-level.patch of Package libvirt.3100

Overview Repositories Revisions Requests Users Attributes Meta

File ba25c214-libxl-log-level.patch of Package libvirt.3100

commit ba25c214f7c622c75448e760f3204844cfff50d0
Author: Jim Fehlig <jfehlig@suse.com>
Date:   Tue Sep 15 08:17:44 2015 -0600

libxl: open libxl log stream with libvirtd log_level
    
    Instead of a hardcoded DEBUG log level, use the overall
    daemon log level specified in libvirtd.conf when opening
    a log stream with libxl. libxl is very verbose when DEBUG
    log level is set, resulting in huge log files that can
    potentially fill a disk. Control of libxl verbosity should
    be placed in the administrator's hands.

Index: libvirt-1.2.18.4/src/libxl/libxl_conf.c
===================================================================
--- libvirt-1.2.18.4.orig/src/libxl/libxl_conf.c
+++ libvirt-1.2.18.4/src/libxl/libxl_conf.c
@@ -1495,6 +1495,7 @@ libxlDriverConfigNew(void)
 {
     libxlDriverConfigPtr cfg;
     char *log_file = NULL;
+    xentoollog_level log_level;
     char ebuf[1024];
     unsigned int free_mem;
 
@@ -1539,9 +1540,24 @@ libxlDriverConfigNew(void)
     }
     VIR_FREE(log_file);
 
+    switch (virLogGetDefaultPriority()) {
+    case VIR_LOG_DEBUG:
+        log_level = XTL_DEBUG;
+        break;
+    case VIR_LOG_INFO:
+        log_level = XTL_INFO;
+        break;
+    case VIR_LOG_WARN:
+        log_level = XTL_WARN;
+        break;
+    case VIR_LOG_ERROR:
+        log_level = XTL_ERROR;
+        break;
+    }
+
     cfg->logger =
         (xentoollog_logger *)xtl_createlogger_stdiostream(cfg->logger_file,
-                                      XTL_DEBUG, XTL_STDIOSTREAM_SHOW_DATE);
+                                      log_level, XTL_STDIOSTREAM_SHOW_DATE);
     if (!cfg->logger) {
         VIR_ERROR(_("cannot create logger for libxenlight, disabling driver"));
         goto error;

Places

File ba25c214-libxl-log-level.patch of Package libvirt.3100

Places