-
Bug
-
Resolution: Done
-
None
-
6.2.9
Description of problem:
When creating or modifying the hosts within RHEV it throw the following error:
RHEV:
2017-06-02 10:44:39,413+02 ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-8) []
Operation Failed: [Cannot add VM. Maximum number of cpu per socket exceeded]
Satellite:
2017-06-02 10:44:39 b86ea2db [app] [I] Failed to save: Failed to create a compute sbr-virt-rhv-nested (RHEV) instance ktruf-maxcpu.sysmgmt.lan: Cannot add VM. Maximum number of cpu per socket exceeded
Version-Release number of selected component (if applicable):
6.2.9 Satellite
RHEV 3.6, 4.0, 4.1
How reproducible:
All the time
Steps to Reproduce:
1. Create hosts within Satellite WebUI at RHEV with more then 16 CPUs
2. Get error
Actual results:
VM is not created
Expected results:
Vm is created successfully as per RHEV documentation with up to 240 cores for RHEV 3.6 and 4.0 and 288 for RHEV 4.1
Additional info:
The limits for RHEV is the following:
MaxSocket = 16
MaxNumOfCpuPerSocket = 16
MaxNumOfThreadsPerCpu = 8
Despite the fact that number of cores are limited to 16 it is possible to split it over the virtual sockets so it would have number_of_sockers*number_of_cpus cores.
The correct parameters could be passed to RHEV via API.
Example:
<vm>
<name>testvm2</name>
<cpu>
<topology cores="2" sockets="9"/>
</cpu>
<cluster>
<name>Default</name>
</cluster>
<memory_policy>
<guaranteed>1024</guaranteed>
</memory_policy>
<template>
<name>Blank</name>
</template>
</vm>
In this example number or cores would be 18.
- external trackers