Bug 997000
Summary: | [WA portal] both garunteed memory and disabled ballon can be set together | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Lukas Svaty <lsvaty> |
Component: | ovirt-engine-webadmin-portal | Assignee: | Nobody's working on this, feel free to take it <nobody> |
Status: | CLOSED NOTABUG | QA Contact: | Lukas Svaty <lsvaty> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.3.0 | CC: | acathrow, dfediuck, ecohen, iheim, Rhev-m-bugs, yeylon |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | sla | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-08-20 13:45:15 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: |
Description
Lukas Svaty
2013-08-14 13:05:53 UTC
that would be the default configuration for anyone upgrading a VM with guaranteed memory in 3.2 when cluster moved to 3.3, so i don't see why it should be blocked? User could think that while balloon is disabled guaranteed memory somehow count into memory management of VM. I don't see reason why guaranteed memory should be configurable when balloon is disabled. (In reply to Lukas Svaty from comment #2) > User could think that while balloon is disabled guaranteed memory somehow > count into memory management of VM. > > I don't see reason why guaranteed memory should be configurable when balloon > is disabled. Lukas, First of all Itamar is right, this should be default for upgraded VMs with no balloon device. There are 2 things I'd like to clarify for this context; 1. There's a big difference between a VM having a balloon device, and mom using the balloon device: - By default every new VM will have a balloon device, unless specifically removed by the creator. - MoM ballooning is a cluster level functionality, due to migration implications on a ballooned VM. Be default, all clusters do not use ballooning, as this may be offensive in some setups. So the sane default of the system is for every new VM (and some upgraded ones) to have a balloon device, while it will not be used until the cluster policy will be modified to use balloon optimization. 2. Guaranteed memory is needed for several reasons; - Allow hard limits at host level (unsupported yet). - Scheduling calculations which use the minimum as KSM is optimizing. - Providing a floor for mom during ballooning. In this issue, you need to consider all the above to understand minimum guaranteed is actually needed regardless of the balloon device status. As this data will be used for scheduling and going forward for hard limits. I'm fine with making this explanation a release note to close the issue. |