<div dir="ltr">yes, max memory size is customizabe even for Blank template<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jul 26, 2017 at 4:32 PM, Ladislav Humenik <span dir="ltr">&lt;<a href="mailto:ladislav.humenik@1und1.de" target="_blank">ladislav.humenik@1und1.de</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div 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 &gt; 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&#39;ll just opened an RFE
    <a class="m_-4045376234297607058moz-txt-link-freetext" href="https://bugzilla.redhat.com/show_bug.cgi?id=1475382" target="_blank">https://bugzilla.redhat.com/<wbr>show_bug.cgi?id=1475382</a><br>
    <br>
    Best regards,<br>
    Ladislav Humenik<div><div class="h5"><br>
    <br>
    <div class="m_-4045376234297607058moz-cite-prefix">On 26.07.2017 15:58, Michal Skrivanek
      wrote:<br>
    </div>
    <blockquote type="cite">
      
      <br>
      <div>
        <blockquote type="cite">
          <div>On 26 Jul 2017, at 16:50, Jakub Niedermertl &lt;<a href="mailto:jniederm@redhat.com" target="_blank">jniederm@redhat.com</a>&gt; wrote:</div>
          <br class="m_-4045376234297607058Apple-interchange-newline">
          <div>
            <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" target="_blank">https://bugzilla.redhat.com/<wbr>enter_bug.cgi?product=ovirt-<wbr>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">&lt;<a href="mailto:ladislav.humenik@1und1.de" target="_blank">ladislav.humenik@1und1.de</a>&gt;</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 -&gt; 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&#39;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 &#39;Blank&#39;;<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 &#39;vm-hotplug%&#39;;<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>
                </blockquote>
              </div>
            </div>
          </div>
        </blockquote>
        <div><br>
        </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>
        </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><br>
        </div>
      </div>
      <div>Thanks,</div>
      <div>michal</div>
      <div><br>
        <blockquote type="cite">
          <div>
            <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>
                  Kind Regards,<br>
                  Ladislav Humenik, System administrator<br>
                  <br>
                </blockquote>
              </div>
              <br>
            </div>
            ______________________________<wbr>_________________<br>
            Users mailing list<br>
            <a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
            <a class="m_-4045376234297607058moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br>
          </div>
        </blockquote>
      </div>
      <br>
    </blockquote>
    <br>
    </div></div><pre class="m_-4045376234297607058moz-signature" cols="72">-- 
Ladislav Humenik

System administrator / VI
IT Operations Hosting Infrastructure

1&amp;1 Internet SE | Ernst-Frey-Str. 5 | 76135 Karlsruhe | Germany
Phone: <a href="tel:+49%20721%20913748361" value="+49721913748361" target="_blank">+49 721 91374-8361</a>
E-Mail: <a class="m_-4045376234297607058moz-txt-link-abbreviated" href="mailto:ladislav.humenik@1und1.de" target="_blank">ladislav.humenik@1und1.de</a> | Web: <a class="m_-4045376234297607058moz-txt-link-abbreviated" href="http://www.1und1.de" target="_blank">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>
  </div>

</blockquote></div><br></div>