Bug 1262871 - [Doc] [VMM] VM and cluster memory settings is not clear
Summary: [Doc] [VMM] VM and cluster memory settings is not clear
Keywords:
Status: CLOSED DUPLICATE of bug 1302661
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation
Version: 3.5.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: rhev-docs@redhat.com
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-14 13:52 UTC by Jiri Belka
Modified: 2019-05-07 13:13 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-14 07:27:14 UTC
oVirt Team: Docs
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jiri Belka 2015-09-14 13:52:22 UTC
Description of problem:

1. Virtual Machine Resource Allocation Settings Explained in unclear.
   How are is 'Memory Allocation' 'Guaranteed Memory' settings related to KSM,
   balloon driver or to cluster's 'Memory Optimization -> None|Server 
   Load|Desktop Load' ???

2. 'Memory Balloon Device Enabled'
   What's effect of having 'Memory Balloon Device Enabled' enabled when it is
   disabled on cluster?

3. cluster's 'Memory Optimization'
   Unclear if this is related to KSM, ballooning or swaping

We have no idea how all this relates to various components. Thus it needs precise explanation.

Version-Release number of selected component (if applicable):
3.5.4

How reproducible:
100%

Steps to Reproduce:
1. read above described doc and try to have 100% sure idea how it works
2.
3.

Actual results:
unclear, not precisely described memory settings for VM/cluster

Expected results:
precise and clear documentation understandable even for average user

Additional info:

Comment 1 Yaniv Lavi 2016-05-09 11:02:53 UTC
oVirt 4.0 Alpha has been released, moving to oVirt 4.0 Beta target.

Comment 5 Yaniv Lavi 2017-02-07 08:18:44 UTC
Can you provide the info request, so we know what needs to be added to the docs?

Comment 7 Yaniv Lavi 2017-02-14 07:27:14 UTC

*** This bug has been marked as a duplicate of bug 1302661 ***


Note You need to log in before you can comment on or make changes to this bug.