Bug 1388245 – [RFE] Configurable maximum memory size

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1388245 - [RFE] Configurable maximum memory size

Summary:	[RFE] Configurable maximum memory size

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	ovirt-engine
Classification:	oVirt
Component:	Backend.Core (Show other bugs)
Sub Component:
Version:	4.1.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified (vote)
Target Milestone:	ovirt-4.1.0-rc
Target Release:	4.1.0
Assigned To:	jniederm
QA Contact:	Israel Pinto
Docs Contact:

URL:
Whiteboard:
Keywords:	FutureFeature

Depends On:	1422546
Blocks:	RHV4.1PPC 1415592
	Show dependency tree / graph

Reported:	2016-10-24 16:28 EDT by jniederm
Modified:	2017-03-16 10:48 EDT (History)
CC List:	10 users (show)

See Also:	1430451
Fixed In Version:
Doc Type:	Enhancement
Doc Text:	This release adds the ability to specify a Maximum Memory value in all VM-like dialogs (Virtual Machine, Template, Pool, and Instance Type). It is accessible in the `{vm, template, instance_type}/memory_policy/max` tag in the REST API. The value defines the upper limit to which memory hot plug can be performed. The default value is 4x memory size.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2017-03-16 10:48:44 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	Virt
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Flags:	michal.skrivanek: ovirt‑4.1? ipinto: testing_plan_complete+ jniederm: planning_ack? michal.skrivanek: devel_ack+ ipinto: testing_ack+

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Knowledge Base (Solution)	2788261	None	None	None	2017-03-09 03:34 EST
oVirt gerrit	65979	master	MERGED	core: Update machine type to rhel 7.3 version	2016-12-06 03:46 EST
oVirt gerrit	66215	master	MERGED	core: VmBase#maxMemorySizeMb property added	2016-12-16 04:31 EST
oVirt gerrit	66319	master	MERGED	MemoryPolicy#max property added	2016-11-16 02:47 EST
oVirt gerrit	66323	master	MERGED	MemoryPolicy#max is of type long	2016-11-09 13:22 EST
oVirt gerrit	67746	master	ABANDONED	core: VM max memory - DAO + entities	2016-12-06 05:49 EST
oVirt gerrit	67747	master	MERGED	core: VM max memory added	2016-12-16 04:30 EST
oVirt gerrit	67748	master	MERGED	restapi: VM max memory added	2016-12-16 04:31 EST
oVirt gerrit	67749	master	MERGED	webadmin: VM max memory added	2016-12-16 04:30 EST
oVirt gerrit	67870	master	MERGED	core: VM maxMemory sent to VDSM	2016-12-16 04:31 EST

Groups: None (edit)

Description jniederm 2016-10-24 16:28:29 EDT

Allow to configure maximum memory size per VM. The value should default to 4x memory size.

Currently max mem size is set by global config values VM32BitMaxMemorySizeInMB, VM64BitMaxMemorySizeInMB and VMPpc64BitMaxMemorySizeInMB to 1048576MB which prevents hot memory unplug from working.

Comment 3 Israel Pinto 2017-03-14 07:52:57 EDT

Verify with:
Red Hat Virtualization Manager Version: 4.1.1.3-0.1.el7
Host:
OS Version:RHEL - 7.3 - 7.el7
Kernel Version:3.10.0 - 550.el7.x86_64
KVM Version:2.6.0 - 28.el7_3.3.1
LIBVIRT Version:libvirt-2.0.0-10.el7_3.5
VDSM Version:vdsm-4.19.7-1.el7ev
SPICE Version:0.12.4 - 20.el7_3
run test plan all pass

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