Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 684077

Summary:	libvirtd.log size increases hugely
Product:	Red Hat Enterprise Linux 6	Reporter:	zhanghaiyan <yoyzhang>
Component:	libvirt	Assignee:	Daniel Veillard <veillard>
Status:	CLOSED NOTABUG	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:
Priority:	low
Version:	6.1	CC:	berrange, dyuan, eblake, llim, xen-maint
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-03-11 07:54:03 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description zhanghaiyan 2011-03-11 02:43:24 UTC

Description of problem:
After set log_level = 1 in /etc/libvirt/libvirtd.conf, libvirtd.log files increased to 29G only in 2 days while I didn't do much libvirt operation on that host.

Version-Release number of selected component (if applicable):
- libvirt-0.8.7-10.el6.x86_64
 log_outputs="1:file:/tmp/libvirtd.log"

How reproducible:
always

Steps to Reproduce:
1. Edit /etc/libvirt/libvirtd.conf
log_level = 1
log_outputs="1:file:/tmp/libvirtd.log"
  
Actual results:
In 2 days, libvirtd.log increased to 29G

Expected results:
Don't increase so hugely

Additional info:

Comment 2 zhanghaiyan 2011-03-11 07:54:03 UTC

Per IRC talking with jdenemar, it is expected behaviour since having virt-manager running means that you actually do a lot with libvirt. Every second or so virt-manager tries to get update on domains status.
So close this as not a bug.

Comment 3 Daniel Berrangé 2011-03-11 10:52:22 UTC

As a further note, setting  log_debug=1 is almost *never* the right thing todo. You are always better off selectively enabled just the debug areas you want, eg

  log_filters="1:qemu 1:security 1:util"
  log_outputs="1:file:/some/file.log"