Bug 1017832
Summary: | [RFE] ksmtuned and /sys/kernel/mm/ksm/run do not respect RHEV-M GUI settings | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Robert McSwain <rmcswain> | ||||
Component: | ovirt-engine-webadmin-portal | Assignee: | Doron Fediuck <dfediuck> | ||||
Status: | CLOSED DUPLICATE | QA Contact: | Pavel Stehlik <pstehlik> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 3.2.0 | CC: | acathrow, dfediuck, ecohen, fdeutsch, iheim, mavital, milan.zelenka, Rhev-m-bugs, rmcswain, sherold, yeylon | ||||
Target Milestone: | --- | Keywords: | FutureFeature, Triaged | ||||
Target Release: | --- | Flags: | sherold:
Triaged+
|
||||
Hardware: | Unspecified | ||||||
OS: | Linux | ||||||
Whiteboard: | sla | ||||||
Fixed In Version: | Doc Type: | Enhancement | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2014-01-06 15:44:56 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | SLA | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Robert McSwain
2013-10-10 15:13:02 UTC
Customer has also confirmed that this is seen on the hypervisor build of Red Hat Enterprise Virtualization Hypervisor release 6.4 (20130912.1.el6_4) Hi Robert, There's a misunderstanding here I'd like to clarify. KSM daemon activity is handled by vdsm and the configured thresholds. RHEV-M only reports KSM activity but does not control it. The current design is to let KSM always work using this policy. You can see a related issue here: https://bugzilla.redhat.com/show_bug.cgi?id=854027#c11 The Cluster UI dialog you're referring to, handles the scheduling considerations. So if, for example, you select server utilization (150%), when running a VM the scheduler will consider up to 150% of the available memory for the relevant hosts. In your case it will use only the reported available memory disallowing memory over-commitment. Can you explain more about your need to disable ksm even if not being considered by the RHEV-M engine? Doron, Sure thing! I'll confirm the customer's need for this and let you know what he has to say as soon as possible. Thanks! Here's the information from the customer ~~~ We have 1 host cluster with only 1 VM (bigger MS SQL database and we need to separate it). KSM function is not desirable and unnecessary in this scenario, because it consumes system resources. We are seeing memory sharing is active and 2% of memory is shared in the RHEV-M. I think that if I set policy of memory page sharing to "None", ksmtuned can be active but it shouldn't share any RAM. ~~~ Is the customer mistaken about how the memory page sharing option of "None" works? Created attachment 828273 [details] mem-share Hi, Attaching the tool tip to show that we're actually explaining that these settings are about the amount of VMs you may run using memory sharing. So if needed you can manually disable ksm in the hosts. Going forward (3.4) we'll add a special setting for it in the UI, based on bug 1026980. |