# Enable full debug logging for monolithic libvirtd # tail 
/etc/libvirt/libvirtd.conf log_level = 1 log_filters="1:*" 
log_outputs="1:file:/var/log/libvirt/libvirtd.log" 

# Enable full debug logging for modular QEMU daemon # tail 
/etc/libvirt/virtqemud.conf log_level = 1 log_filters="1:*" 
log_outputs="1:file:/var/log/libvirt/virtqemud.log" 

# Restart only the daemon architecture currently in use
systemctl restart libvirtd.service       # monolithic mode
# OR
systemctl restart virtqemud.service      # modular mode

In general, use either:
libvirtd.service for monolithic mode, or virtqemud plus the appropriate modular 
supporting daemons for modular mode.

/var/log/libvirt/
├── libvirtd.log        # host-wide monolithic daemon log
├── virtqemud.log       # host-wide modular QEMU daemon log
└── qemu/
    ├── vm1.log         # VM-specific QEMU process log
    ├── vm2.log
    └── ...
        
/var/log/libvirt stores host-level libvirt daemon logs, such as libvirtd.log 
for monolithic mode or virtqemud.log for modular QEMU mode. 
The /var/log/libvirt/qemu directory stores VM-specific QEMU logs. 
Therefore, placing virtqemud.log under /var/log/libvirt is appropriate.

The existing logrotate configuration includes /var/log/libvirt/libvirtd.log 
through /etc/logrotate.d/libvirtd, and all VM-specific log files matching 
/var/log/libvirt/qemu/*.log through /etc/logrotate.d/libvirtd.qemu.

It does not currently include /var/log/libvirt/virtqemud.log; therefore, a 
separate logrotate rule must be added for virtqemud.log if that log is enabled.

We should either place virtqemud.log under /var/log/libvirt/qemu/, which is not 
appropriate because that directory is intended for VM-specific logs.
The virtqemud.log rotation rule can be added to /etc/logrotate.d/libvirtd.qemu, 
or or define a dedicated logrotate rule in a separate file such as 
/etc/logrotate.d/virtqemud.

Example rule:

/var/log/libvirt/virtqemud.log {
    weekly

    missingok
    rotate 4
    compress
    delaycompress
    copytruncate
    minsize 100k
}

This would provide the same log-management behavior for modular virtqemud file 
logging, that is already available for monolithic libvirtd logging.

Reply via email to