Bug 1946876

Summary:	automatic Maximum Memory exceeds possible maximum on new VM dialog
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Steffen Froemer <sfroemer>
Component:	ovirt-engine	Assignee:	Lucia Jelinkova <ljelinko>
Status:	CLOSED ERRATA	QA Contact:	Guilherme Santos <gdeolive>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.4.4	CC:	ahadas, dfodor, mavital, sgratch
Target Milestone:	ovirt-4.4.7
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	ovirt-engine-4.4.7.4	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-07-22 15:12:33 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:

Description Steffen Froemer 2021-04-07 06:19:39 UTC

Description of problem:


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


How reproducible:


Steps to Reproduce:
1. Open new VM dialog
2. Set 'Memory Size' to 4TB
3.

Actual results:
The values for max Memory will be set to '16777216 MB' which is 4 times higher than configured Memory size. Although it does exceed the maximum configured memory of engine.
This will block VM creation. 

Expected results:
The MaxMemory value should be set to the value which is configured in VM64BitMaxMemorySizeInMB. On default to '6291456'

Additional info:

# engine-config -g VM64BitMaxMemorySizeInMB
VM64BitMaxMemorySizeInMB: 6291456 version: 4.2
VM64BitMaxMemorySizeInMB: 6291456 version: 4.4
VM64BitMaxMemorySizeInMB: 6291456 version: 4.3
VM64BitMaxMemorySizeInMB: 6291456 version: 4.5

Comment 5 Guilherme Santos 2021-06-28 18:06:29 UTC

Verified on:
rhvm-4.4.7.4-0.9.el8ev.noarch

Steps:
1. # engine-config -g VM64BitMaxMemorySizeInMB
Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false
VM64BitMaxMemorySizeInMB: 6291456 version: 4.2
VM64BitMaxMemorySizeInMB: 6291456 version: 4.3
VM64BitMaxMemorySizeInMB: 6291456 version: 4.4
VM64BitMaxMemorySizeInMB: 6291456 version: 4.5
VM64BitMaxMemorySizeInMB: 16777216 version: 4.6

2. Open new VM dialog
3. Set 'Memory Size' to 5,6,7... TB

Results:
Calculated maximum does not exceed VM64BitMaxMemorySizeInMB (16777216 in this case)

Comment 10 errata-xmlrpc 2021-07-22 15:12:33 UTC

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 (Moderate: RHV Manager (ovirt-engine) security update [ovirt-4.4.7]), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:2865

Comment 11 meital avital 2022-08-03 11:38:50 UTC

Due to QE capacity, we are not going to cover this issue in our automation