Bug 1841083
| Summary: | bump up max memory limit to 6TB | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Michal Skrivanek <michal.skrivanek> |
| Component: | BLL.Virt | Assignee: | Michal Skrivanek <michal.skrivanek> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Beni Pelled <bpelled> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.4.0 | CC: | bugs, sgoodman |
| Target Milestone: | ovirt-4.4.1 | Flags: | pm-rhel:
ovirt-4.4+
|
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | rhv-4.4.1-3 | Doc Type: | Enhancement |
| Doc Text: |
With this update, the maximum memory size for 64-bit virtual machines based on x86_64 or ppc64/ppc64le architectures is now 6 TB. This limit also applies to virtual machines based on x86_64 architecture in 4.2 and 4.3 Cluster Levels.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-07-08 08:25:18 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1831031 | ||
|
Description
Michal Skrivanek
2020-05-28 10:37:03 UTC
increasing for POWER too. Shouldbe safe enough, though due to the issues on RHEL7 with POWER8 and POWER9 and RHEL-ALT I'd rather keep it at current value there (in 4.2,4.3 clusters) and only increase in 4.4 Verified with: - ovirt-engine-4.4.1.2-0.10.el8ev.noarch Verification steps: 1. # engine-config -g VM64BitMaxMemorySizeInMB VM64BitMaxMemorySizeInMB: 6291456 version: 4.2 VM64BitMaxMemorySizeInMB: 6291456 version: 4.3 VM64BitMaxMemorySizeInMB: 6291456 version: 4.4 2. Create a VM with 6TB RAM This bugzilla is included in oVirt 4.4.1 release, published on July 8th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.1 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |