<div dir="ltr"><div><div><div><div>Hello Ladislav,<br><br></div>the function computing size of default maximum memory size is currently not configurable from DB.<br><br></div>If you want it to be so please feel free to file an RFE [1].<br><br>[1]: <a href="https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine">https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine</a><br><br></div>Best regards,<br></div>Jakub<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jul 26, 2017 at 1:59 PM, Ladislav Humenik <span dir="ltr"><<a href="mailto:ladislav.humenik@1und1.de" target="_blank">ladislav.humenik@1und1.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hallo, after engine update to 4.1.2 from 4.0.6 we have following bug<br>
<br>
*Your Future Description: *<br>
<br>
Maximum memory value is stored in |VmBase.maxMemorySizeMb| property. It is validated against range [/memory of VM/, /*MaxMemorySizeInMB/], where /*MaxMemorySizeInMB/ is one of |VM32BitMaxMemorySizeInMB|, |VM64BitMaxMemorySizeInMB| and |VMPpc64BitMaxMemorySizeInMB| configuration options depending on selected operating system of the VM. Default value in webadmin UI is 4x size of memory.<br>
<br>
During migration of engine 4.0 -> 4.1 all VM-like entities will get max memory = 4x memory.<br>
<br>
If a VM (or template) is imported (from export domain, snapshot, external system) and doesn't have max memory set yet, the maximum value of max memory is set (|*MaxMemorySizeInMB| config options).<br>
<br>
*Our engine settings:*<br>
[root@ovirt]# engine-config -g VM64BitMaxMemorySizeInMB<br>
VM64BitMaxMemorySizeInMB: 8388608 version: 4.1<br>
VM64BitMaxMemorySizeInMB: 8388608 version: 3.6<br>
VM64BitMaxMemorySizeInMB: 8388608 version: 4.0<br>
[root@ovirt# engine-config -g VM32BitMaxMemorySizeInMB<br>
VM32BitMaxMemorySizeInMB: 20480 version: general<br>
<br>
*Template:<br>
*engine=# select vm_guid,vm_name,mem_size_mb,ma<wbr>x_memory_size_mb from vm_static where vm_name LIKE 'Blank';<br>
vm_guid | vm_name | mem_size_mb | max_memory_size_mb<br>
------------------------------<wbr>--------+---------+-----------<wbr>--+--------------------<br>
00000000-0000-0000-0000-00000<wbr>0000000 | Blank | 8192 | 32768<br>
(1 row)<br>
<br>
*Created VM*<br>
- expected is mem_size_mb * VM64BitMaxMemorySizeInMB<br>
- we get mem_size_mb * 4 (default)<br>
<br>
*Engine: *engine=# select vm_guid,vm_name,mem_size_mb,ma<wbr>x_memory_size_mb from vm_static where vm_name LIKE 'vm-hotplug%';<br>
vm_guid | vm_name | mem_size_mb | max_memory_size_mb<br>
------------------------------<wbr>--------+-------------+-------<wbr>------+--------------------<br>
254a0c61-3c0a-41e7-a2ec-5f77c<wbr>abbe533 | vm-hotplug | 1024 | 4096<br>
c0794a03-58ba-4e68-8f43-e0320<wbr>032830c | vm-hotplug2 | 3072 | 12288<br>
(2 rows)<br>
<br>
*Question:*<br>
It is possible to change this (default * 4) behavior in DB??<br>
<br>
Kind Regards,<br>
Ladislav Humenik, System administrator<br>
<br>
</blockquote></div><br></div>