[ovirt-users] cannot exceed maximum memory size

[Juan Hernández]

On 03/09/2017 04:00 PM, Jakub Niedermertl wrote:
> Based on the snipped provided at the beginning of the conversation I
> assume rest api v3 is used. I'm not sure, max memory property was
> backported there.
> 
> @Juan do we have some support for 4.1 changes in rest api v3?
> 
> In rest api v4 it's
> http://ovirt.github.io/ovirt-engine-api-model/4.1/#types/memory_policy/attributes/max
> .
> 
> <vm>
>     ...
>     <memory_policy>
>         <max>amount in bytes</max>
>         ...
>     </memory_policy>
>     ...
> </vm>
> 

Max memory is a version 4 feature, it isn't/won't be available in
version 3 of the API.

> 
> 
> On Thu, Mar 9, 2017 at 3:07 PM, Marcelo Leandro <marceloltmm at gmail.com> wrote:
>> Thanks for reply Jakub Niedermertl,
>>
>>      I would like the explicitly specifying in my script , but i dont know
>> the parameters for use for max memory.
>> Can you help me ?
>>
>> Very Thanks.
>>
>> 2017-03-09 10:37 GMT-03:00 Jakub Niedermertl <jniederm at redhat.com>:
>>>
>>> Hi all,
>>>
>>> Since engine 4.1 there is new property of VMs/templates - max memory
>>> [1] that is required to be larger than (or equal to) memory size. The
>>> problem is probably caused by the fact that the specified memory (I
>>> assume that value of  `memo` is 20480MB) is larger that max memory
>>> that is implicitly copied from template (Blank in this case). I can
>>> see two possible solutions:
>>> * Explicitly specifying size of max memory in the script.
>>> * Increasing max memory in the template.
>>>
>>> Jakub
>>>
>>> [1]:
>>> http://www.ovirt.org/develop/release-management/features/engine/maximum-memory-size/
>>>
>>> On Thu, Mar 9, 2017 at 2:20 PM, Shahar Havivi <shavivi at redhat.com> wrote:
>>>> its not related to bug 1425089 (which is upgrading cluster issue) but
>>>> its
>>>> the same feature that cause this issue,
>>>> Jakub what do we have bug on that issue?
>>>>
>>>> as for the default RAM limit you can find it via the engine-config tool:
>>>> $ engine-config -g VM32BitMaxMemorySizeInMB
>>>> $ engine-config -g VM64BitMaxMemorySizeInMB
>>>>
>>>> On Thu, Mar 9, 2017 at 2:44 PM, Maton, Brett <matonb at ltresources.co.uk>
>>>> wrote:
>>>>>
>>>>> I have a similar problem creating VM's with the API, but no solution.
>>>>>
>>>>>   It seems that by default oVirt uses custom 'Instance Type' ( you can
>>>>> see
>>>>> it if you use the UI to create a VM ).
>>>>>   The default RAM limit for custom Instance Type is 4096MB.
>>>>>
>>>>>   I haven't found where you can change the settnigs for the custom
>>>>> instance type though.
>>>>>
>>>>>
>>>>>
>>>>> On 9 March 2017 at 11:52, Marcelo Leandro <marceloltmm at gmail.com>
>>>>> wrote:
>>>>>>
>>>>>> can someone help me?
>>>>>>
>>>>>> 2017-03-07 16:25 GMT-03:00 Marcelo Leandro <marceloltmm at gmail.com>:
>>>>>>>
>>>>>>> Hello ,
>>>>>>>
>>>>>>> I am have an script that create VM , after upgrade to 4.1 I have this
>>>>>>> erro when trying create a new VM:
>>>>>>>
>>>>>>> detail: Cannot add VM. Memory size (20480MB) cannot exceed maximum
>>>>>>> memory size (4096MB).
>>>>>>>
>>>>>>> my commando fore create VM :
>>>>>>>
>>>>>>> api.vms.add(params.VM(name="teste", memory=memo , cpu=cpu,
>>>>>>> cluster=api.clusters.get(cluster),
>>>>>>> template=api.templates.get('Blank'),
>>>>>>> type_="server"))
>>>>>>>
>>>>>>> I dont how specific  the maximum memory size.
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> Marcelo Leandro
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Users mailing list
>>>>>> Users at ovirt.org
>>>>>> http://lists.ovirt.org/mailman/listinfo/users
>>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Users mailing list
>>>>> Users at ovirt.org
>>>>> http://lists.ovirt.org/mailman/listinfo/users
>>>>>
>>>>
>>
>>