Red Hat Bugzilla – Bug 957729
[RFE] Expose VM Limit config values to rhevm-config
Last modified: 2015-09-22 09:09 EDT
VM maximum CPU and memory config values should be user editable with rhevm-config
workarounds: 1. change the db directly (not recommended). 2. use rhevm-config with an alternate property file with the requested property to change
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.
(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
and what about the CPU? To define Max number of VCPUs? per user or global or..?
(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
memory is covered by os info. for cpu, lets add to property file, and later consider if to move to osinfo as well.
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.
andrew, lets avoid confusion - please specify the config keys you want exposed
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
merged to master: http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=40eba07416ad106095b4a64b8a3641dab23dba7a
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
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
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