Bug 957729

Summary:	[RFE] Expose VM Limit config values to rhevm-config
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Andrew Cathrow <acathrow>
Component:	RFEs	Assignee:	Frantisek Kobzik <fkobzik>
Status:	CLOSED ERRATA	QA Contact:	Ilanit Stein <istein>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	3.3.0	CC:	abaron, acathrow, iheim, lpeer, michal.skrivanek, pstehlik, rbalakri
Target Milestone:	---	Keywords:	FutureFeature, Improvement
Target Release:	3.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	virt
Fixed In Version:	is3	Doc Type:	Enhancement
Doc Text:	A virtual machine's memory limit can be edited using the VM64BitMaxMemorySizeInMB, VM32BitMaxMemorySizeInMB and VMMinMemorySizeInMB options in rhevm-config. Likewise, a virtual machine's maximum number of CPUs can be edited using the MaxNumOfCpuPerSocket, MaxNumOfVmCpus, and MaxNumOfVmSockets options.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-01-21 17:19:40 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Andrew Cathrow 2013-04-29 12:04:07 UTC

VM maximum CPU and memory config values should be user editable with rhevm-config

Comment 1 Itamar Heim 2013-04-29 13:47:48 UTC

workarounds:
1. change the db directly (not recommended).
2. use rhevm-config with an alternate property file with the requested property to change

Comment 2 Michal Skrivanek 2013-06-12 11:40:38 UTC

is the intent to limit it per OS? If so we can do that with OS info integration in OS config files. System wide still, though.

Comment 3 Andrew Cathrow 2013-06-12 11:43:23 UTC

(In reply to Michal Skrivanek from comment #2)
> is the intent to limit it per OS? If so we can do that with OS info
> integration in OS config files. System wide still, though.

No, in this BZ just to allow the setting to be changed by the user using engine-config

Comment 4 Michal Skrivanek 2013-06-12 12:32:38 UTC

and what about the CPU? To define Max number of VCPUs? per user or global or..?

Comment 5 Michal Skrivanek 2013-06-12 12:39:06 UTC

(In reply to Andrew Cathrow from comment #3)
> No, in this BZ just to allow the setting to be changed by the user using
> engine-config
ok - so what I'm asking is whether "OS info" integration instead where you can configure it per OS is good enough.
...and the previous comment

Comment 6 Itamar Heim 2013-06-13 11:02:38 UTC

memory is covered by os info.
for cpu, lets add to property file, and later consider if to move to osinfo as well.

Comment 7 Andrew Cathrow 2013-06-13 11:08:28 UTC

I don't believe OS info is relevant here.
The first step is to make sure that our virtual hardware limits are accessible.
That's different to guest limits.

Comment 8 Itamar Heim 2013-06-13 11:57:59 UTC

andrew, lets avoid confusion - please specify the config keys you want exposed

Comment 9 Michal Skrivanek 2013-06-14 10:07:40 UTC

for CPU we have: MaxNumOfCpuPerSocket, MaxNumOfVmCpus, MaxNumOfVmSockets
for memory: VM32BitMaxMemorySizeInMB, VM64BitMaxMemorySizeInMB and a minimum limit VMMinMemorySizeInMB

those 2 max memory limits are not currently exposed

Comment 10 Michal Skrivanek 2013-06-26 10:31:19 UTC

merged to master:
http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=40eba07416ad106095b4a64b8a3641dab23dba7a

Comment 11 Ilanit Stein 2013-07-15 06:33:21 UTC

Verified on is5, that all config values detailed on comment #9, can be user editable. 
Shouldn't be any validation/limit on the values themselves?


[root@istein-33 yum.repos.d]# engine-config -g MaxNumOfCpuPerSocket
MaxNumOfCpuPerSocket: 16 version: 3.0
MaxNumOfCpuPerSocket: 16 version: 3.1
MaxNumOfCpuPerSocket: 16 version: 3.2
MaxNumOfCpuPerSocket: 16 version: 3.3
[root@istein-33 yum.repos.d]# engine-config -g MaxNumOfVmCpus MaxNumOfCpuPerSocket
MaxNumOfVmCpus: 160 version: 3.1
MaxNumOfVmCpus: 160 version: 3.2
MaxNumOfVmCpus: 160 version: 3.3
MaxNumOfVmCpus: 64 version: 3.0
[root@istein-33 yum.repos.d]# engine-config -g MaxNumOfVmCpus
MaxNumOfVmCpus: 160 version: 3.1
MaxNumOfVmCpus: 160 version: 3.2
MaxNumOfVmCpus: 160 version: 3.3
MaxNumOfVmCpus: 64 version: 3.0
[root@istein-33 yum.repos.d]# engine-config -g MaxNumOfVmSockets
MaxNumOfVmSockets: 16 version: 3.0
MaxNumOfVmSockets: 16 version: 3.1
MaxNumOfVmSockets: 16 version: 3.2
MaxNumOfVmSockets: 16 version: 3.3
[root@istein-33 yum.repos.d]# engine-config -g VM32BitMaxMemorySizeInMB
VM32BitMaxMemorySizeInMB: 20480 version: general
[root@istein-33 yum.repos.d]# engine-config -g VM64BitMaxMemorySizeInMB
VM64BitMaxMemorySizeInMB: 524288 version: 3.0
VM64BitMaxMemorySizeInMB: 2097152 version: 3.1
VM64BitMaxMemorySizeInMB: 2097152 version: 3.2
VM64BitMaxMemorySizeInMB: 2097152 version: 3.3
[root@istein-33 yum.repos.d]# engine-config -g VMMinMemorySizeInMB
VMMinMemorySizeInMB: 256 version: general
[root@istein-33 yum.repos.d]# engine-config -s VM64BitMaxMemorySizeInMB=2097150
Please select a version:
1. 3.0
2. 3.1
3. 3.2
4. 3.3
2
[root@istein-33 yum.repos.d]# engine-config -g VM64BitMaxMemorySizeInMB
VM64BitMaxMemorySizeInMB: 524288 version: 3.0
VM64BitMaxMemorySizeInMB: 2097150 version: 3.1
VM64BitMaxMemorySizeInMB: 2097152 version: 3.2
VM64BitMaxMemorySizeInMB: 2097152 version: 3.3
[root@istein-33 yum.repos.d]# engine-config -s VM64BitMaxMemorySizeInMB=2097152
Please select a version:
1. 3.0
2. 3.1
3. 3.2
4. 3.3
2
[root@istein-33 yum.repos.d]# engine-config -g VM64BitMaxMemorySizeInMB
VM64BitMaxMemorySizeInMB: 524288 version: 3.0
VM64BitMaxMemorySizeInMB: 2097152 version: 3.1
VM64BitMaxMemorySizeInMB: 2097152 version: 3.2
VM64BitMaxMemorySizeInMB: 2097152 version: 3.3
[root@istein-33 yum.repos.d]# engine-config -s MaxNumOfVmCpus=160000
Please select a version:
1. 3.1
2. 3.2
3. 3.3
4. 3.0
2
[root@istein-33 yum.repos.d]# engine-config -g VM64BitMaxMemorySizeInMB
VM64BitMaxMemorySizeInMB: 524288 version: 3.0
VM64BitMaxMemorySizeInMB: 2097152 version: 3.1
VM64BitMaxMemorySizeInMB: 2097152 version: 3.2
VM64BitMaxMemorySizeInMB: 2097152 version: 3.3
[root@istein-33 yum.repos.d]# engine-config -g MaxNumOfVmCpus
MaxNumOfVmCpus: 160 version: 3.1
MaxNumOfVmCpus: 160000 version: 3.2
MaxNumOfVmCpus: 160 version: 3.3
MaxNumOfVmCpus: 64 version: 3.0
[root@istein-33 yum.repos.d]# engine-config -s MaxNumOfVmCpus=160
Please select a version:
1. 3.1
2. 3.2
3. 3.3
4. 3.0

Please select a version:
1. 3.1
2. 3.2
3. 3.3
4. 3.0
2
[root@istein-33 yum.repos.d]# engine-config -g MaxNumOfVmCpus
MaxNumOfVmCpus: 160 version: 3.1
MaxNumOfVmCpus: 160 version: 3.2
MaxNumOfVmCpus: 160 version: 3.3
MaxNumOfVmCpus: 64 version: 3.0

Comment 12 Michal Skrivanek 2013-07-15 07:13:25 UTC

it's a separate application so it won't do the same check as the engine backend would do. This tool is for semi-supported stuff which you shouldn't normally touch

Comment 14 errata-xmlrpc 2014-01-21 17:19:40 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, and where to find the updated
files, follow the link below.

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

http://rhn.redhat.com/errata/RHSA-2014-0038.html