Red Hat Bugzilla – Bug 726014
Fix memleak on exit in virtio-balloon
Last modified: 2013-01-09 19:09:52 EST
Description of problem: Unplugging a virtio-balloon device or exiting qemu doesn't free some RAM. Adding an exit handler that calls virtio_cleanup() fixes the leak.
Verification of this bug is blocked by bug 736975.
According to: https://bugzilla.redhat.com/show_bug.cgi?id=736975#c8 Bug 736975 has been fixed. Reproduce and verify using steps in: https://bugzilla.redhat.com/show_bug.cgi?id=726020#c7 Since from qemu 160, all version suffers from bug 736975, cannot reproduce this as a contrast, just verify the patch. Verify on qemu-kvm-0.12.1.2-2.193.el6.x86_64: used free buffers/cached 181 7281 0/6 <---before start qemu 735 6726 0/9 <---start qemu 731 6730 0/9 <---after hotplug/unplug 300 times 182 7279 0/6 <---after exit qemu According to above results, the patch works fine, verified. However, there is another issue, once i did 300 times hotplug/unplug and check the result next morning, the used/free memory are 914/6547, i did two times more and check the result immediately after it finished, it looks like above one, seems when idle, qemu-kvm has memory leak? I will investigate this further. Any advice please let me know.
(In reply to comment #6) > According to: > https://bugzilla.redhat.com/show_bug.cgi?id=736975#c8 > > Bug 736975 has been fixed. > > Reproduce and verify using steps in: > https://bugzilla.redhat.com/show_bug.cgi?id=726020#c7 > > Since from qemu 160, all version suffers from bug 736975, cannot reproduce this > as a contrast, just verify the patch. > > Verify on qemu-kvm-0.12.1.2-2.193.el6.x86_64: > > used free buffers/cached > 181 7281 0/6 <---before start qemu > 735 6726 0/9 <---start qemu > 731 6730 0/9 <---after hotplug/unplug 300 times > 182 7279 0/6 <---after exit qemu > > According to above results, the patch works fine, verified. > > However, there is another issue, once i did 300 times hotplug/unplug and check > the result next morning, the used/free memory are 914/6547, i did two times > more and check the result immediately after it finished, it looks like above > one, seems when idle, qemu-kvm has memory leak? I will investigate this > further. Any advice please let me know. I will set this issue as verified.about the potential issue,if you can identify it,please spilt it.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2011-1531.html