Bug 967572
| Summary: | PRD33 - mom integration - balloon to try and get memory up to guaranteed memory | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Itamar Heim <iheim> |
| Component: | RFEs | Assignee: | Martin Sivák <msivak> |
| Status: | CLOSED ERRATA | QA Contact: | Lukas Svaty <lsvaty> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.1.0 | CC: | acathrow, adahms, chetan, dfediuck, iheim, jturner, lpeer, oramraz, yeylon, zdover |
| Target Milestone: | --- | Keywords: | FutureFeature |
| Target Release: | 3.3.0 | Flags: | lsvaty:
testing_plan_complete-
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | sla | ||
| Fixed In Version: | is7 | Doc Type: | Release Note |
| Doc Text: |
This feature makes it possible to use virtio balloons for memory optimization.
Every virtual machine in clusters with a compatibility level of 3.2 and higher includes a balloon device unless that device is specifically removed. This balloon device requires guest drivers and a guest agent to control the balloon size.
Ballooning optimization is a cluster-level policy attribute, which is disabled by default. To have a balloon running, the virtual machine must have a balloon device with the relevant drivers, and the cluster it belongs to must enable ballooning optimization. Each host in the cluster receives a balloon policy update when the status of that host changes to 'Up'. A manual option is also available for emergencies that makes it possible to force an update for a specific host.
Once this is set, MoM will start ballooning where and when possible to allow memory over-commitment, with a limitation of the guaranteed memory size that every virtual machine has.
Note that in some scenarios ballooning may collide with KSM. In such cases, MoM will attempt to adjust the balloon size to minimize collisions. Additionally, in some scenarios ballooning may cause sub-optimal performance for a virtual machine. Administrators are advised to use ballooning optimization with caution.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-01-21 17:23:41 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1019470 | ||
|
Description
Itamar Heim
2013-05-27 13:28:52 UTC
how do we test this? - Configure a VM with 2 GB RAM, and 1 GB guaranteed memory.
- Make sure MoM has its balloon policy working.
- use vdsClient to get VM stats. You should be able to see the balloon stats and verify it does not exceed the minimum guaranteed you defined.
balloonInfo = {'balloon_max': 3145728, 'balloon_cur': 3145728}
Hi Doron, please review the 'Doc Text' for accuracy. Thank you! (In reply to Cheryn Tan from comment #6) > Hi Doron, please review the 'Doc Text' for accuracy. Thank you! Done. Much appreciated! 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/RHSA-2014-0038.html |