Bug 619711
| Summary: | Memory leak in libvirtd | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | RHEL Program Management <pm-rhel> |
| Component: | libvirt | Assignee: | Daniel Veillard <veillard> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 5.4 | CC: | chris.lober, eblake, hbrock, herrold, james.brown, jdenemar, jentrena, jialiu, juzhang, jwest, laine, mjenner, nachandr, pbonzini, plyons, pm-eus, samuel.kielek, smayhew, tao, virt-maint, xen-maint |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | libvirt-0.6.3-33.el5_5.3 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-08-10 17:03:11 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: | |||
| Bug Depends On: | 590073 | ||
| Bug Blocks: | |||
|
Description
RHEL Program Management
2010-07-30 09:15:21 UTC
Fix built into libvirt-0.6.3-33.el5_5.3 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. 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. http://rhn.redhat.com/errata/RHSA-2010-0615.html |