Bug 1841083 - bump up max memory limit to 6TB
Summary: bump up max memory limit to 6TB
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.4.1
: ---
Assignee: Michal Skrivanek
QA Contact: Beni Pelled
URL:
Whiteboard:
Depends On:
Blocks: 1831031
TreeView+ depends on / blocked
 
Reported: 2020-05-28 10:37 UTC by Michal Skrivanek
Modified: 2020-07-28 14:15 UTC (History)
2 users (show)

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.
Clone Of:
Environment:
Last Closed: 2020-07-08 08:25:18 UTC
oVirt Team: Virt
Embargoed:
pm-rhel: ovirt-4.4+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 109328 0 master MERGED increase max memory limit to 6TB 2020-09-21 13:14:37 UTC

Description Michal Skrivanek 2020-05-28 10:37:03 UTC 
we tested SAP workloads with 6TB so we can safely increase the limit(it's a soft limit anyway)
Comment 2 Michal Skrivanek 2020-05-29 08:23:46 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
Comment 3 Beni Pelled 2020-06-16 13:50:36 UTC 
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
Comment 4 Sandro Bonazzola 2020-07-08 08:25:18 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.