On Wed, Feb 05, 2014 at 10:13:56AM -0500, Yogev Rabl wrote:
This is not a bug.
Even though the configuration looks empty, the *default* log_level is 3,
i.e.  warnings and errors, this is redirected to systemd journal (on
systems that are run systemd, and to syslog on older systems). You can
notice this when you invoke:
   $ systemctl status libvirtd
    libvirtd.service - Virtualization daemon
       Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled)
       Active: active (running) since Wed 2014-02-05 22:45:05 IST; 11s ago
     Main PID: 32521 (libvirtd)
       CGroup: /system.slice/libvirtd.service
               ├─  821 /sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf
               └─32521 /usr/sbin/libvirtd
    Feb 05 22:45:05 
foohost.com systemd[1]: Started Virtualization daemon.
    Feb 05 22:45:06 
foohost.com dnsmasq[821]: read /etc/hosts - 2 addresses
    Feb 05 22:45:06 
foohost.com dnsmasq[821]: read
/var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
    Feb 05 22:45:06 
foohost.com dnsmasq-dhcp[821]: read
/var/lib/libvirt/dnsmasq/default.hostsfile
Furthermore, there's a couple of different ways to enable various log
levels based on filters, etc.
- If you want logs to be redirected to a file, that can be expressed in
  /etc/libvirt/libvirtd.conf. 
   To log _everything_ (this spews LOTS of details, fills up your disk),
   add these 
        log_level = 1
        log_outputs = 1:file:/var/tmp/libvirtd.log
   to /etc/libvirt/libvirtd.conf, restart libvirtd.
- Alternatively, you can set environment variables (if set, this will
  take precedence over values specified in the configuration file):
    $ export LIBVIRT_DEBUG=1
    $ export  LIBVIRT_TRACE=1
More extensive details on logging filters are available here:
     
http://libvirt.org/logging.html
 
--
/kashyap