[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [Rdo-list] libvirtd default configuration



Perry,

in current setups nothing is logged at all, i.e there is no libvirt log until we configure the conf file to log something... And sorry, but I disagree with Dan... working on ovirt for a few years I can tell you that the libvirt logs are in debug and are simply rotated and deleted if space is run out or after 30 days. These are simple debugging tools that admin's need and if someone decided that they don't need them - that's ok, but our premise should be that we want to catch events since they cannot always be reproduced...

this is from an ovirt host where log level is debug and logs are rotated:

2014-02-05 17:07:31.556+0000: 31964: debug : virConnectNumOfDomains:1855 : conn=0x7fe7140008c0 2014-02-05 17:07:35.775+0000: 31958: debug : virConnectCompareCPU:17082 : conn=0x7fe7140008c0, xmlDesc=<cpu match="minimum"><model>Haswell</model><vendor>Intel</vendor></cpu>, flags=0 2014-02-05 17:07:35.786+0000: 31959: debug : virConnectCompareCPU:17082 : conn=0x7fe7140008c0, xmlDesc=<cpu match="minimum"><model>athlon</model><vendor>AMD</vendor></cpu>, flags=0 2014-02-05 17:07:35.787+0000: 31966: debug : virConnectCompareCPU:17082 : conn=0x7fe7140008c0, xmlDesc=<cpu match="minimum"><model>Nehalem</model><vendor>Intel</vendor></cpu>, flags=0 2014-02-05 17:07:35.792+0000: 31963: debug : virConnectCompareCPU:17082 : conn=0x7fe7140008c0, xmlDesc=<cpu match="minimum"><model>Conroe</model><vendor>Intel</vendor></cpu>, flags=

root XXX-XXXX ~]# ls -l /var/log/libvirt/
total 34384
-rw-------. 1 root root 14934506 Feb  5 19:07 libvirtd.log
-rw-------. 1 root root    52868 Jan  1 10:40 libvirtd.log.100.xz
-rw-------. 1 root root   150216 Jan  6 08:25 libvirtd.log.10.xz
-rw-------. 1 root root   149048 Jan  6 06:55 libvirtd.log.11.xz
-rw-------. 1 root root   148444 Jan  6 05:25 libvirtd.log.12.xz
-rw-------. 1 root root   149484 Jan  6 03:55 libvirtd.log.13.xz
-rw-------. 1 root root   150536 Jan  6 02:25 libvirtd.log.14.xz
-rw-------. 1 root root   149948 Jan  6 00:55 libvirtd.log.15.xz
-rw-------. 1 root root   148748 Jan  5 23:25 libvirtd.log.16.xz
-rw-------. 1 root root   149548 Jan  5 21:55 libvirtd.log.17.xz
-rw-------. 1 root root   149428 Jan  5 20:25 libvirtd.log.18.xz
-rw-------. 1 root root   149284 Jan  5 18:55 libvirtd.log.19.xz
-rw-------. 1 root root   601460 Jan 23 14:25 libvirtd.log.1.xz
-rw-------. 1 root root   265132 Dec 15 03:48 libvirtd.log-20131215.xz
-rw-------. 1 root root   148028 Jan  3 03:09 libvirtd.log-20140103.xz
-rw-------. 1 root root   148916 Jan  5 17:25 libvirtd.log.20.xz
-rw-------. 1 root root   149680 Jan  5 15:55 libvirtd.log.21.xz
-rw-------. 1 root root   244180 Jan  5 14:25 libvirtd.log.22.xz
-rw-------. 1 root root   164292 Jan  5 13:10 libvirtd.log.23.xz
-rw-------. 1 root root   156920 Jan  5 11:55 libvirtd.log.24.xz
-rw-------. 1 root root   148544 Jan  5 10:40 libvirtd.log.25.xz
-rw-------. 1 root root   149344 Jan  5 09:10 libvirtd.log.26.xz


On 02/05/2014 06:28 PM, Perry Myers wrote:
On 02/05/2014 01:23 PM, Dafna Ron wrote:
This is a bug since we install with packstack which need to configure
this in the deployment and up until now was configured.
libvirtd log should be created and should be in debug level when
installing with packstack.
If this did not happen - it's a bug and user should not configure it
manually.
libvirtd should never be configured in debug mode by default.  Please
see danpb's rationale here:

https://bugzilla.redhat.com/show_bug.cgi?id=1061753#c3

If someone wanted to change packstack to expose a configuration option
to set libvirtd to more verbose logging (but not debug mode) if that
config param is set, that would be fine.  But under no circumstances
should it be defaulted to debug enabled.



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]