Hide Forgot
Description of problem: the memory usage graphic on the VM detail window is wrong. as VM is stopped, the memory usage graphic of it should says ZERO usage, but it show that the VM consumes some memory. Version-Release number of selected component (if applicable): virt-manager-0.8.6-2.el6.noarch Steps to Reproduce: 1.open the virtual machine manager 2.Double click at one stopped VM item to open its' details window. 3.switch into the virtual hardware details tab on the VM details windows and click "performance" button, it will show the problem Actual results: the memory usage GRAPHIC show non-ZERO usage to a stopped VM Expected results: the memory usage GRAPHIC show ZERO usage to a stopped VM Additional info: a screenshot was attached
Since RHEL 6.1 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
Deferring to 6.2
Fixed upstream: http://git.fedorahosted.org/git?p=virt-manager.git;a=commit;h=77384e00b415c3ebd23a8b05098bc14a59a0498f
Fixed in virt-manager-0.9.0-2.el6
Verified PASS in below environment: # uname -r 2.6.32-165.el6.x86_64 qemu-kvm-0.12.1.2-2.175.el6.x86_64 libvirt-0.9.4-0rc1.2.el6.x86_64 virt-manager-0.9.0-5.el6.x86_64 Steps: 1. For a shutdown guest, I check performance info in guest details page. Now memory usage graphic display Zero usage. Details please refer to Screenshot-after.png --- I can reproduce this bug with virt-manager-0.8.6-4.el6.noarch. Please refer to Screenshot-before.png
Created attachment 516442 [details] Screenshot-before.png
Created attachment 516443 [details] Screenshot-after.png
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 description necessary
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/RHBA-2011-1642.html