<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hello, thank you for fast response.<br>
<br>
The point of changing the max_mem_size is little tricky, as we have
environments with together ~13k VMs running on top of ovirt, no
kidding :) and currently doing upgrades from 3.6 > 4.1. So we can
easy set those values to the needed ones for every VM, thats not a
big deal. <br>
<br>
However, I was just hoping it is editable without changing/modifying
our current API calls, for any newly created VM (as this is the
reason for asking for help), somewhere in engine-config or in DB.<br>
<br>
I'll just opened an RFE
<a class="moz-txt-link-freetext" href="https://bugzilla.redhat.com/show_bug.cgi?id=1475382">https://bugzilla.redhat.com/show_bug.cgi?id=1475382</a><br>
<br>
Best regards,<br>
Ladislav Humenik<br>
<br>
<div class="moz-cite-prefix">On 26.07.2017 15:58, Michal Skrivanek
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:E3517D5C-CFAC-49E3-8EB8-18327664F0CD@redhat.com">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<br class="">
<div>
<blockquote type="cite" class="">
<div class="">On 26 Jul 2017, at 16:50, Jakub Niedermertl <<a
href="mailto:jniederm@redhat.com" class=""
moz-do-not-send="true">jniederm@redhat.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">
<div class="">
<div class="">
<div class="">
<div class="">Hello Ladislav,<br class="">
<br class="">
</div>
the function computing size of default maximum
memory size is currently not configurable from DB.<br
class="">
<br class="">
</div>
If you want it to be so please feel free to file an
RFE [1].<br class="">
<br class="">
[1]: <a
href="https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine"
class="" moz-do-not-send="true">https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine</a><br
class="">
<br class="">
</div>
Best regards,<br class="">
</div>
Jakub<br class="">
</div>
<div class="gmail_extra"><br class="">
<div class="gmail_quote">On Wed, Jul 26, 2017 at 1:59 PM,
Ladislav Humenik <span dir="ltr" class=""><<a
href="mailto:ladislav.humenik@1und1.de"
target="_blank" class="" moz-do-not-send="true">ladislav.humenik@1und1.de</a>></span>
wrote:<br class="">
<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 class="">
<br class="">
*Your Future Description: *<br class="">
<br class="">
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="">
<br class="">
During migration of engine 4.0 -> 4.1 all VM-like
entities will get max memory = 4x memory.<br class="">
<br class="">
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="">
<br class="">
*Our engine settings:*<br class="">
[root@ovirt]# engine-config -g
VM64BitMaxMemorySizeInMB<br class="">
VM64BitMaxMemorySizeInMB: 8388608 version: 4.1<br
class="">
VM64BitMaxMemorySizeInMB: 8388608 version: 3.6<br
class="">
VM64BitMaxMemorySizeInMB: 8388608 version: 4.0<br
class="">
[root@ovirt# engine-config -g VM32BitMaxMemorySizeInMB<br
class="">
VM32BitMaxMemorySizeInMB: 20480 version: general<br
class="">
<br class="">
*Template:<br class="">
*engine=# select vm_guid,vm_name,mem_size_mb,ma<wbr
class="">x_memory_size_mb from vm_static where
vm_name LIKE 'Blank';<br class="">
vm_guid | vm_name |
mem_size_mb | max_memory_size_mb<br class="">
------------------------------<wbr class="">--------+---------+-----------<wbr
class="">--+--------------------<br class="">
00000000-0000-0000-0000-00000<wbr class="">0000000 |
Blank | 8192 | 32768<br class="">
(1 row)<br class="">
<br class="">
*Created VM*<br class="">
- expected is mem_size_mb * VM64BitMaxMemorySizeInMB<br
class="">
- we get mem_size_mb * 4 (default)<br class="">
<br class="">
*Engine: *engine=# select
vm_guid,vm_name,mem_size_mb,ma<wbr class="">x_memory_size_mb
from vm_static where vm_name LIKE 'vm-hotplug%';<br
class="">
vm_guid | vm_name |
mem_size_mb | max_memory_size_mb<br class="">
------------------------------<wbr class="">--------+-------------+-------<wbr
class="">------+--------------------<br class="">
254a0c61-3c0a-41e7-a2ec-5f77c<wbr class="">abbe533 |
vm-hotplug | 1024 | 4096<br
class="">
c0794a03-58ba-4e68-8f43-e0320<wbr class="">032830c |
vm-hotplug2 | 3072 | 12288<br
class="">
(2 rows)<br class="">
<br class="">
*Question:*<br class="">
It is possible to change this (default * 4) behavior
in DB??<br class="">
</blockquote>
</div>
</div>
</div>
</blockquote>
<div><br class="">
</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 “Blank” I think, Jakube?</div>
<div>That’s for the default case, you can change that any way you
like for the concrete VM you’re 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="">
</div>
<div>the VM[64|32]BitMaxMemorySizeInMB values are for the total
maximum the particular qemu we ship supports, it’s not
anything you should need to change.</div>
<div class=""><br class="">
</div>
</div>
<div>Thanks,</div>
<div>michal</div>
<div><br class="">
<blockquote type="cite" class="">
<div class="">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<br class="">
Kind Regards,<br class="">
Ladislav Humenik, System administrator<br class="">
<br class="">
</blockquote>
</div>
<br class="">
</div>
_______________________________________________<br class="">
Users mailing list<br class="">
<a href="mailto:Users@ovirt.org" class=""
moz-do-not-send="true">Users@ovirt.org</a><br class="">
<a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a><br class="">
</div>
</blockquote>
</div>
<br class="">
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Ladislav Humenik
System administrator / VI
IT Operations Hosting Infrastructure
1&1 Internet SE | Ernst-Frey-Str. 5 | 76135 Karlsruhe | Germany
Phone: +49 721 91374-8361
E-Mail: <a class="moz-txt-link-abbreviated" href="mailto:ladislav.humenik@1und1.de">ladislav.humenik@1und1.de</a> | Web: <a class="moz-txt-link-abbreviated" href="http://www.1und1.de">www.1und1.de</a>
Hauptsitz Montabaur, Amtsgericht Montabaur, HRB 24498
Vorstand: Robert Hoffmann, Hans-Henning Kettler, Uwe Lamnek, Matthias Steinberg
Aufsichtsratsvorsitzender: René Obermann
Member of United Internet
Diese E-Mail kann vertrauliche und/oder gesetzlich geschützte Informationen enthalten. Wenn Sie nicht der bestimmungsgemäße Adressat sind oder diese E-Mail irrtümlich erhalten haben, unterrichten Sie bitte den Absender und vernichten Sie diese E-Mail. Anderen als dem bestimmungsgemäßen Adressaten ist untersagt, diese E-Mail zu speichern, weiterzuleiten oder ihren Inhalt auf welche Weise auch immer zu verwenden.
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient of this e-mail, you are hereby notified that saving, distribution or use of the content of this e-mail in any way is prohibited. If you have received this e-mail in error, please notify the sender and delete the e-mail.</pre>
</body>
</html>