--Apple-Mail=_FF88E3A6-895D-41CC-8024-B994EDCC2E63 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8
On 26 Jul 2017, at 16:50, Jakub Niedermertl <jniederm@redhat.com> = wrote: =20 Hello Ladislav, =20 the function computing size of default maximum memory size is = currently not configurable from DB. =20 If you want it to be so please feel free to file an RFE [1]. =20 [1]: https://bugzilla.redhat.com/enter_bug.cgi?product=3Dovirt-engine = <https://bugzilla.redhat.com/enter_bug.cgi?product=3Dovirt-engine> =20 Best regards, Jakub =20 On Wed, Jul 26, 2017 at 1:59 PM, Ladislav Humenik = <ladislav.humenik@1und1.de <mailto:ladislav.humenik@1und1.de>> wrote: Hallo, after engine update to 4.1.2 from 4.0.6 we have following bug =20 *Your Future Description: * =20 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. =20 During migration of engine 4.0 -> 4.1 all VM-like entities will get = max memory =3D 4x memory. =20 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). =20 *Our engine settings:* [root@ovirt]# engine-config -g VM64BitMaxMemorySizeInMB VM64BitMaxMemorySizeInMB: 8388608 version: 4.1 VM64BitMaxMemorySizeInMB: 8388608 version: 3.6 VM64BitMaxMemorySizeInMB: 8388608 version: 4.0 [root@ovirt# engine-config -g VM32BitMaxMemorySizeInMB VM32BitMaxMemorySizeInMB: 20480 version: general =20 *Template: *engine=3D# select vm_guid,vm_name,mem_size_mb,max_memory_size_mb from = vm_static where vm_name LIKE 'Blank'; vm_guid | vm_name | mem_size_mb | = max_memory_size_mb = --------------------------------------+---------+-------------+-----------=
00000000-0000-0000-0000-000000000000 | Blank | 8192 | = 32768 (1 row) =20 *Created VM* - expected is mem_size_mb * VM64BitMaxMemorySizeInMB - we get mem_size_mb * 4 (default) =20 *Engine: *engine=3D# select = vm_guid,vm_name,mem_size_mb,max_memory_size_mb from vm_static where = vm_name LIKE 'vm-hotplug%'; vm_guid | vm_name | mem_size_mb | = max_memory_size_mb = --------------------------------------+-------------+-------------+-------=
254a0c61-3c0a-41e7-a2ec-5f77cabbe533 | vm-hotplug | 1024 | = 4096 c0794a03-58ba-4e68-8f43-e0320032830c | vm-hotplug2 | 3072 | = 12288 (2 rows) =20 *Question:* It is possible to change this (default * 4) behavior in DB??
if the issue is with GUI then setting the max memory in the template = would be inherited to all VMs from that template, you can even change = that in =E2=80=9CBlank=E2=80=9D I think, Jakube? That=E2=80=99s for the default case, you can change that any way you = like for the concrete VM you=E2=80=99re creating. if the issue is with API you can simply provide any number for the max = mem in all the requests the VM[64|32]BitMaxMemorySizeInMB values are for the total maximum the = particular qemu we ship supports, it=E2=80=99s not anything you should = need to change. Thanks, michal
=20 Kind Regards, Ladislav Humenik, System administrator =20 =20 _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
--Apple-Mail=_FF88E3A6-895D-41CC-8024-B994EDCC2E63 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 <html><head><meta http-equiv=3D"Content-Type" content=3D"text/html = charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; = -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" = class=3D""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div = class=3D"">On 26 Jul 2017, at 16:50, Jakub Niedermertl <<a = href=3D"mailto:jniederm@redhat.com" class=3D"">jniederm@redhat.com</a>>= wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div = dir=3D"ltr" class=3D""><div class=3D""><div class=3D""><div = class=3D""><div class=3D"">Hello Ladislav,<br class=3D""><br = class=3D""></div>the function computing size of default maximum memory = size is currently not configurable from DB.<br class=3D""><br = class=3D""></div>If you want it to be so please feel free to file an RFE = [1].<br class=3D""><br class=3D"">[1]: <a = href=3D"https://bugzilla.redhat.com/enter_bug.cgi?product=3Dovirt-engine" = class=3D"">https://bugzilla.redhat.com/enter_bug.cgi?product=3Dovirt-engin= e</a><br class=3D""><br class=3D""></div>Best regards,<br = class=3D""></div>Jakub<br class=3D""></div><div class=3D"gmail_extra"><br = class=3D""><div class=3D"gmail_quote">On Wed, Jul 26, 2017 at 1:59 PM, = Ladislav Humenik <span dir=3D"ltr" class=3D""><<a = href=3D"mailto:ladislav.humenik@1und1.de" target=3D"_blank" = class=3D"">ladislav.humenik@1und1.de</a>></span> wrote:<br = class=3D""><blockquote class=3D"gmail_quote" style=3D"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 class=3D""> <br class=3D""> *Your Future Description: *<br class=3D""> <br class=3D""> 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 class=3D""> <br class=3D""> During migration of engine 4.0 -> 4.1 all VM-like entities will get = max memory =3D 4x memory.<br class=3D""> <br class=3D""> 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 class=3D"">= <br class=3D""> *Our engine settings:*<br class=3D""> [root@ovirt]# engine-config -g VM64BitMaxMemorySizeInMB<br class=3D""> VM64BitMaxMemorySizeInMB: 8388608 version: 4.1<br class=3D""> VM64BitMaxMemorySizeInMB: 8388608 version: 3.6<br class=3D""> VM64BitMaxMemorySizeInMB: 8388608 version: 4.0<br class=3D""> [root@ovirt# engine-config -g VM32BitMaxMemorySizeInMB<br class=3D""> VM32BitMaxMemorySizeInMB: 20480 version: general<br class=3D""> <br class=3D""> *Template:<br class=3D""> *engine=3D# select vm_guid,vm_name,mem_size_mb,ma<wbr = class=3D"">x_memory_size_mb from vm_static where vm_name LIKE = 'Blank';<br class=3D""> vm_guid = | vm_name | mem_size_mb = | max_memory_size_mb<br class=3D""> ------------------------------<wbr = class=3D"">--------+---------+-----------<wbr = class=3D"">--+--------------------<br class=3D""> 00000000-0000-0000-0000-00000<wbr class=3D"">0000000 | Blank = | 8192 | = 32768<br class=3D""> (1 row)<br class=3D""> <br class=3D""> *Created VM*<br class=3D""> - expected is mem_size_mb * VM64BitMaxMemorySizeInMB<br class=3D""> - we get mem_size_mb * 4 (default)<br class=3D""> <br class=3D""> *Engine: *engine=3D# select vm_guid,vm_name,mem_size_mb,ma<wbr = class=3D"">x_memory_size_mb from vm_static where vm_name LIKE = 'vm-hotplug%';<br class=3D""> vm_guid = | = vm_name | mem_size_mb | max_memory_size_mb<br = class=3D""> ------------------------------<wbr = class=3D"">--------+-------------+-------<wbr = class=3D"">------+--------------------<br class=3D""> 254a0c61-3c0a-41e7-a2ec-5f77c<wbr class=3D"">abbe533 | = vm-hotplug | 1024 | = 4096<br class=3D""> c0794a03-58ba-4e68-8f43-e0320<wbr class=3D"">032830c | vm-hotplug2 = | 3072 | = 12288<br class=3D""> (2 rows)<br class=3D""> <br class=3D""> *Question:*<br class=3D""> It is possible to change this (default * 4) behavior in DB??<br = class=3D""></blockquote></div></div></div></blockquote><div><br = class=3D""></div></div><div>if the issue is with GUI then setting the = max memory in the template would be inherited to all VMs from that = template, you can even change that in =E2=80=9CBlank=E2=80=9D I think, = Jakube?</div><div>That=E2=80=99s for the default case, you can change = that any way you like for the concrete VM you=E2=80=99re = creating.</div><div><div>if the issue is with API you can simply provide = any number for the max mem in all the requests</div><div><br = class=3D""></div><div>the VM[64|32]BitMaxMemorySizeInMB values are for = the total maximum the particular qemu we ship supports, it=E2=80=99s not = anything you should need to change.</div><div class=3D""><br = class=3D""></div></div><div>Thanks,</div><div>michal</div><div><br = class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div = class=3D"gmail_extra"><div class=3D"gmail_quote"><blockquote = class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc = solid;padding-left:1ex"> <br class=3D""> Kind Regards,<br class=3D""> Ladislav Humenik, System administrator<br class=3D""> <br class=3D""> </blockquote></div><br class=3D""></div> _______________________________________________<br class=3D"">Users = mailing list<br class=3D""><a href=3D"mailto:Users@ovirt.org" = class=3D"">Users@ovirt.org</a><br = class=3D"">http://lists.ovirt.org/mailman/listinfo/users<br = class=3D""></div></blockquote></div><br class=3D""></body></html>= --Apple-Mail=_FF88E3A6-895D-41CC-8024-B994EDCC2E63--