Bug 619711 - Memory leak in libvirtd
Summary: Memory leak in libvirtd
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: libvirt
Version: 5.4
Hardware: x86_64
OS: Linux
Target Milestone: rc
: ---
Assignee: Daniel Veillard
QA Contact: Virtualization Bugs
Keywords: ZStream
Depends On: 590073
TreeView+ depends on / blocked
Reported: 2010-07-30 09:15 UTC by RHEL Product and Program Management
Modified: 2013-01-11 03:09 UTC (History)
21 users (show)

Clone Of:
Last Closed: 2010-08-10 17:03:11 UTC

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2010:0615 normal SHIPPED_LIVE Low: libvirt security and bug fix update 2010-08-10 17:02:33 UTC

Description RHEL Product and Program Management 2010-07-30 09:15:21 UTC
This bug has been copied from bug #590073 and has been proposed
to be backported to 5.5 z-stream (EUS).

Comment 3 Jiri Denemark 2010-07-30 12:13:49 UTC
Fix built into libvirt-0.6.3-33.el5_5.3

Comment 5 Johnny Liu 2010-08-03 04:23:15 UTC
Verify this bug with libvirt-0.6.3-33.el5_5.3 on RHEL5u5 Server x86_64 Xen, RHEL5u5 Client i386 and RHEL5u5 Server ia64, and PASSED.

1. Update xen to xen-3.0.3-114.el5, libvirt to libvirt-0.6.3-33.el5_5.3;
2. Restart xend and libvirtd service.
3. Open two terminal.
4. On one terminal, run "while true; do echo connect; done | virsh", 
which will repeatedly connect and disconnect to/from libvirtd.
The connect/disconnect loop is not the best way to trigger this leak but seems
to be the easiest one and it shows quite fast.
5. On the other terminal, run "top -d1 -p $(pidof libvirtd)" to watch memory consumption of libvirtd, take note the value of RES column.

With the new package the memory remain more-or-less steady, it sometimes stay unchanged for a while or even go down. So this bug is fixed.

Comment 6 errata-xmlrpc 2010-08-10 17:03:11 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.