On Wed, Jan 21, 2015 at 12:12:14PM +, Daniel P. Berrange wrote:
[..snip..]
So I'm intending to create a standalone virtlogd daemon to address this
problem. Similarly to virtlockd, it will be able to re-exec itelf so
that upgrades can be done with no interruption to logging, and libvirtd
With QEMU there are a couple of areas where QEMU ends up logging data
to a file on the host.
- stdout/err - connected to /var/log/libvirt/qemu/$GUEST.log
- serial/parallel/console when used with type=file
The stdout/err is typically very small, typically only getting data when
an error occurs
Very good idea!
2015-01-21 15:12 GMT+03:00 Daniel P. Berrange berra...@redhat.com:
With QEMU there are a couple of areas where QEMU ends up logging data
to a file on the host.
- stdout/err - connected to /var/log/libvirt/qemu/$GUEST.log
- serial/parallel/console when used with type=file