Bug 798497
Summary: | Plug memory leak on migration | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Alex Jia <ajia> |
Component: | libvirt | Assignee: | Osier Yang <jyang> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.3 | CC: | acathrow, dallan, dyuan, mzhan, rwu, weizhan |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | libvirt-0.9.10-6.el6 | Doc Type: | Bug Fix |
Doc Text: |
No documentation needed.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2012-06-20 06:49:18 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
Alex Jia
2012-02-29 03:37:52 UTC
Alex, do you have a patch for this one? (In reply to comment #1) > Alex, do you have a patch for this one? Hello Dave, I'm trying to find a right place to fix the leak firstly. Regards, Alex patch posted internally, move to POST. http://post-office.corp.redhat.com/archives/rhvirt-patches/2012-March/msg01476.html Osier, can you describe the leak? Is the leak in virsh or the daemon or both, and what action by the user causes the leak to occur? Is it an error path or a normal use case? (In reply to comment #6) > Osier, can you describe the leak? Is the leak in virsh or the daemon or both, > and what action by the user causes the leak to occur? Is it an error path or a > normal use case? It's leak in remote driver, so each libvirt client will leak, no leak in daemon. It's not a error path, just a normal use case will cause that. Ok, given that, we need to fix this in 6.3. (In reply to comment #8) > Ok, given that, we need to fix this in 6.3. Yes, it's leak after every migration operation. Verify pass on libvirt-0.9.10-6.el6.x86_64 qemu-kvm-0.12.1.2-2.246.el6.x86_64 kernel-2.6.32-250.el6.x86_64 Start a guest without cache=none for its disk No memory leak after migration with --unsafe ==17411== LEAK SUMMARY: ==17411== definitely lost: 0 bytes in 0 blocks 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: No documentation needed. 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-2012-0748.html |