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.
Starting and shutting down a domain led to a memory leak due to the memory buffer not being freed properly. With this update, starting and shutting down a domain no longer leads to a memory leak.
Verified. Do not found issue so far.
Please confirm if the "LEAK SUMMARY" is acceptable. I will continue to run the
script and try to finish more cycles.
Test environment:
libvirt: libvirt-0.8.1-27.el6_0.3
kernel: kernel-2.6.32-71.16.1.el6
qemu-kvm: qemu-kvm-0.12.1.2-2.113.el6_0.6
Steps:
1. install a domain named "rhel6-clone"
2. disable selinux:
# setenforce 0
3. run "libvirtd_memory_check.sh" attachment script
4. check the "libvirtd_memory_check.sh.log" after running 400 cycles, do not
found leak again.
-------------------
==4191== LEAK SUMMARY:
==4191== definitely lost: 0 bytes in 0 blocks
==4191== indirectly lost: 0 bytes in 0 blocks
==4191== possibly lost: 349 bytes in 18 blocks
==4191== still reachable: 1,840 bytes in 39 blocks
==4191== suppressed: 0 bytes in 0 blocks
==4191== Rerun with --leak-check=full to see details of leaked memory
==4191==
==4191== For counts of detected and suppressed errors, rerun with: -v
==4191== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 6 from 6)
More than 3000 cycles have been done, did not find any memory leak so far. The scription will continue to run.
-------------
==4191== HEAP SUMMARY:
==4191== in use at exit: 2,189 bytes in 57 blocks
==4191== total heap usage: 93 allocs, 36 frees, 108,711 bytes allocated
==4191==
==4191== LEAK SUMMARY:
==4191== definitely lost: 0 bytes in 0 blocks
==4191== indirectly lost: 0 bytes in 0 blocks
==4191== possibly lost: 349 bytes in 18 blocks
==4191== still reachable: 1,840 bytes in 39 blocks
==4191== suppressed: 0 bytes in 0 blocks
==4191== Rerun with --leak-check=full to see details of leaked memory
==4191==
==4191== For counts of detected and suppressed errors, rerun with: -v
==4191== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 6 from 6)
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/RHBA-2011-0446.html
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Starting and shutting down a domain led to a memory leak due to the memory buffer not being freed properly. With this update, starting and shutting down a domain no longer leads to a memory leak.