Bug 1427844 - [downstream clone - 3.6.11] Block memory over-commitment when KSM and ballooning are not being used
Summary: [downstream clone - 3.6.11] Block memory over-commitment when KSM and balloon...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 4.0.5
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-3.6.11
: ---
Assignee: Jenny Tokar
QA Contact: Shira Maximov
URL:
Whiteboard:
Depends On: 1402838
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-01 11:44 UTC by rhev-integ
Modified: 2021-08-30 13:22 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, it was possible to set memory overcommit without enabling either Kernel Same-page Merging (KSM) or memory ballooning. As a result, the scheduler used the requested optimization but Red Hat Virtualization Host was unable to perform memory overcommit. In this update, it is no long er possible to set memory overcommit without enabling KSM or memory ballooning.
Clone Of: 1402838
Environment:
Last Closed: 2017-05-09 17:04:08 UTC
oVirt Team: SLA
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-43259 0 None None None 2021-08-30 12:42:47 UTC
Red Hat Knowledge Base (Solution) 2808171 0 None None None 2017-03-01 11:45:09 UTC
Red Hat Product Errata RHEA-2017:1210 0 normal SHIPPED_LIVE Red Hat Enterprise Virtualization Manager 3.6.11 2017-05-09 21:03:09 UTC
oVirt gerrit 73766 0 ovirt-engine-3.6 ABANDONED core: Allow memory over commitment only if ksm or ballooning are available 2017-03-13 10:38:46 UTC
oVirt gerrit 73982 0 ovirt-engine-3.6 MERGED core: Allow memory over commitment only if ksm or ballooning are available 2017-03-14 10:02:56 UTC

Description rhev-integ 2017-03-01 11:44:37 UTC 
+++ This bug is a downstream clone. The original bug is: +++
+++   bug 1402838 +++
======================================================================

Description of problem:
Currently we allow memory over-commitment even when KSM and ballooning are not being used. Since there's nothing to create over-commitment, we should not allow this.

Version-Release number of selected component (if applicable):
4.0.5 and below.

How reproducible:


Steps to Reproduce:
1. In edit cluster dialog, go to optimization side tab.
2. Set memory optimization to server load (150%)
3. Disable KSM and Ballooning and approve the settings.

Actual results:
Scheduler will use the requested optimization, although there's nothing
to allow this at the host level.

Expected results:
Disable optimization when ksm and ballooning are unavailable.

Additional info:

(Originally by Doron Fediuck)
Comment 1 rhev-integ 2017-03-01 11:44:44 UTC 
This should consider REST and and GUI, so implementation should be at the engine (CanDoAction during editing and creation).

(Originally by Doron Fediuck)
Comment 7 Shira Maximov 2017-04-03 13:30:27 UTC 
Verify on : 
Red Hat Enterprise Virtualization Manager Version: 3.6.11-0.1.el6

Steps to Reproduce:
1. In edit cluster dialog, go to optimization side tab.
2. Set memory optimization to server load (150%)
3. Disable KSM and Ballooning and approve the settings.

Result: 
Error while executing action: KSM or balooning must be enabled to allow memory optimization.
Comment 9 errata-xmlrpc 2017-05-09 17:04:08 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.

https://access.redhat.com/errata/RHEA-2017:1210
Note You need to log in before you can comment on or make changes to this bug.