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.

=Comment: #0=================================================
Emily J. Ratliff <ratliff.com> - 
1. Feature Overview:
Feature Id:	[202017]
a. Name of Feature:	libvirt control of ksm
b. Feature Description
Add support to libvirt to control and query ksm levels on the host

2. Feature Details:
Sponsor:	LTC
Architectures:
x86
x86_64

Arch Specificity: Both
Delivery Mechanism: Direct from community
Category:	Xen
Request Type:	Package - Feature from Upstream
d. Upstream Acceptance:	In Progress
Sponsor Priority	2
f. Severity: Medium
IBM Confidential:	no
Code Contribution:	3rd party code
g. Component Version Target:	latest version of libvirt

3. Business Case
KSM is an important memory compression technology for KVM that provides for greater VM density on a
given KVM host.  Extending control of KSM to libvirt provies management applications the ability to
control KSM as needed, adjusting to customer workload demands.

4. Primary contact at Red Hat: 
John Jarvis
jjarvis

5. Primary contacts at Partner:
Project Management Contact:
Stephanie Glass, sglass.com, 512-838-9284

Technical contact(s):
Ryan Harper, raharper.com

IBM Manager:
Warren Grunbok II, grunbok.com

The Fedora 12  KVM rpm includes a script for automatically tuning KSM parameters on the fly.

http://www.redhat.com/archives/fedora-virt/2009-September/msg00052.html

Need to evaluate what level of additional manual control might be needed in libvirt itself, if any.

Right now there is no specific KSM libvirt support upstream, though there
have been some discussions of memory overcommit control. But there is
nothing available upstream at this point so the feature is at risk for
RHEL 6.0 GA

Daniel

We are not sure KSM management belongs in libvirt at all. In any case, it is clear that it needs to settle a while longer before we can understand what kind of API it should have.

Deferred this to 6.1 -- we have not yet defined where the correct interface point is for gray-area services like KSM. Once we have done that it will be obvious whether it should have a libvirt API or the API should fall to some other service.

Removing from 6.0 tracker, adding to 6.1 tracker

------- Comment From aliguori.com 2010-10-27 12:43 EDT-------
Given the current interfaces provided by KSM, we no longer feel it's necessary to have a libvirt interface to manage KSM.

Okidoc,

  thanks !

Daniel

------- Comment From mcintire.com 2011-03-04 10:24 EDT-------
IBM is quiting this feature request.