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.

Bug 679668

Summary: virsh dommemstat returns a empty result
Product: Red Hat Enterprise Linux 6 Reporter: Alex Jia <ajia>
Component: libvirtAssignee: Osier Yang <jyang>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1CC: dallan, dyuan, eblake, jyang, llim, xen-maint, yoyzhang, yupzhang
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: libvirt-0.9.3-1.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-06 10:54:45 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 2011-02-23 07:35:28 UTC
Description of problem:
Because of qemu-kvm temporarily disabled guest-provided-stats-on-info-ballon-monitor feature from 112-now version, in fact, libvirt qemu driver doesn't support qemudDomainMemoryStats API now, but the current source codes display it indeed support it in src/qemu/qemu_driver.c:
......
    qemudDomainBlockStats, /* domainBlockStats */
    qemudDomainInterfaceStats, /* domainInterfaceStats */
    qemudDomainMemoryStats, /* domainMemoryStats */
    qemudDomainBlockPeek, /* domainBlockPeek */
    qemudDomainMemoryPeek, /* domainMemoryPeek */
    qemuDomainGetBlockInfo, /* domainGetBlockInfo */
......

So I can successfully run virsh dommemstat on active domain, however, the result is empty, which will let user very confused.

If qemu-kvm doesn't support the feature on rhel6.1 release, IMHO,libvirt should raise a error information at least, it looks this:

error: Unable to get memory statistics
error: qemu driver currently doesn't support the feature


Version-Release number of selected component (if applicable):
# rpm -q libvirt 
libvirt-0.8.7-7.el6.x86_64

# rpm -q qemu-kvm
qemu-kvm-0.12.1.2-2.145.el6.x86_64

# uname -r
2.6.32-113.el6.x86_64

How reproducible:
always, if qemu-kvm version is from 0.12.1.2-2.113 to now

Steps to Reproduce:
1. virsh start domainname
2. virsh dommemstat domainname
  
Actual results:
return a empty value

Expected results:
libvirt raises a friendly prompt information

Additional info:
See also bug 572453

Comment 2 RHEL Program Management 2011-04-04 01:56:48 UTC
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.

Comment 4 Osier Yang 2011-06-03 08:01:38 UTC
patch posted to upstream: http://www.redhat.com/archives/libvir-list/2011-June/msg00156.html

Comment 5 Osier Yang 2011-06-14 05:31:07 UTC
commit 41514f7b3e4eaa18a98976c05fab771fec4ded18
Author: Osier Yang <jyang>
Date:   Tue Jun 14 11:21:35 2011 +0800

    qemu: Parse current balloon value returned by query_balloon
    
    Qemu once supported following memory stats which will returned by
    "query_balloon":
    
        stat_put(dict, "actual", actual);
        stat_put(dict, "mem_swapped_in", dev->stats[VIRTIO_BALLOON_S_SWAP_IN]);
        stat_put(dict, "mem_swapped_out", dev->stats[VIRTIO_BALLOON_S_SWAP_OUT]);
        stat_put(dict, "major_page_faults", dev->stats[VIRTIO_BALLOON_S_MAJFLT]);
        stat_put(dict, "minor_page_faults", dev->stats[VIRTIO_BALLOON_S_MINFLT]);
        stat_put(dict, "free_mem", dev->stats[VIRTIO_BALLOON_S_MEMFREE]);
        stat_put(dict, "total_mem", dev->stats[VIRTIO_BALLOON_S_MEMTOT]);
    
    But it later disabled all the stats except "actual" by commit
    07b0403dfc2b2ac179ae5b48105096cc2d03375a.
    
    libvirt doesn't parse "actual", so user will always see a empty result
    with "virsh dommemstat $domain". Even qemu haven't disabled the stats,
    we should support parsing "actual".

Comment 7 yuping zhang 2011-07-06 07:25:17 UTC
Reproduce this issue on libvirt-0.9.2-1.el6.x86_64
#virsh start rhel6
#virsh dommemstat rhel6
Return Nothing

Tested this issue with:

libvirt-0.9.3-1.el6
qemu-kvm-0.12.1.2-2.167.el6
kernel-2.6.32-164.el6

# virsh list --all
 Id Name                 State
----------------------------------
  1 rhel6                running

# virsh dommemstat rhel6
actual 1048300

# virsh dumpxml rhel6
<domain type='kvm' id='1'>
  <name>rhel6</name>
  <uuid>f66ecb57-f669-b21a-61ab-099d28f74361</uuid>
  <memory>1048570</memory>
  <currentMemory>1048300</currentMemory>
  <vcpu>2</vcpu>
 ......................

So change the bug status to VERIFIED

Comment 8 errata-xmlrpc 2011-12-06 10:54:45 UTC
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-1513.html