+++ This bug was initially created as a clone of Bug #601690 +++
Description of problem:
KVM and libvirt in RHEL6 have support for querying extended memory statistics from the guest kernel balloon driver. The RHEL6 kernel, however, is missing this since IIRC it was only added in 2.6.34. This is causing frequent bug reports from beta testers expecting extended statistics to be present in RHEL6 and is also useful information for host admins. The code is well isolated from the rest of the kernel, so it should be feasible to backport this.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot a RHEL6 KVM guest
2. Run 'virsh dommemstat $GUESTNAME' on the host
Similar output to
# virsh dommemstat f14x86_64
There appear to be at least 3 upstream patches required to provide this support in the kernel virtio balloon driver.
The virtio balloon code in RHEL5 is slightly stale. For getting these patches, we'll also have to either backport other patches (which add new features). Is that desirable for RHEL5?
(In reply to comment #1)
> The virtio balloon code in RHEL5 is slightly stale. For getting these patches,
> we'll also have to either backport other patches (which add new features). Is
> that desirable for RHEL5?
Answering my own question: the same changes (in the common virtio code) were needed by the backport for virtio-console as well, and those changes are now in the RHEL5 tree.
Only the balloon-specific changes now need to be backported, which are a clean backport from upstream for the commits mentioned in the original report. I'm building the kernel and will post patches soon.
Note to QE: the stats enabled here won't be shown due to reverting the functionality as part of bug 623903. If you wish to test this functionality, use a RHEL6 host with a qemu-kvm build < qemu-kvm-0.12.1.2-2.113.el6.
*** Bug 563588 has been marked as a duplicate of this bug. ***
You can download this test kernel from http://people.redhat.com/jwilson/el5
Detailed testing feedback is always welcomed.
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.