1:59 p.m.
Hallo, after engine update to 4.1.2 from 4.0.6 we have following bug
*Your Future Description: *
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.
During migration of engine 4.0 -> 4.1 all VM-like entities will get max
memory = 4x memory.
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).
*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
*Template:
*engine=# 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)
*Created VM*
- expected is mem_size_mb * VM64BitMaxMemorySizeInMB
- we get mem_size_mb * 4 (default)
*Engine: *engine=# 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)
*Question:*
It is possible to change this (default * 4) behavior in DB??
Kind Regards,
Ladislav Humenik, System administrator
3:50 p.m.
Hello Ladislav,
the function computing size of default maximum memory size is currently not
configurable from DB.
If you want it to be so please feel free to file an RFE [1].
[1]: https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine
Best regards,
Jakub
On Wed, Jul 26, 2017 at 1:59 PM, Ladislav Humenik <ladislav.humenik(a)1und1.de
wrote:
Hallo, after engine update to 4.1.2 from 4.0.6 we have following bug
*Your Future Description: *
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.
During migration of engine 4.0 -> 4.1 all VM-like entities will get max
memory = 4x memory.
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).
*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
*Template:
*engine=# 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)
*Created VM*
- expected is mem_size_mb * VM64BitMaxMemorySizeInMB
- we get mem_size_mb * 4 (default)
*Engine: *engine=# 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)
*Question:*
It is possible to change this (default * 4) behavior in DB??
Kind Regards,
Ladislav Humenik, System administrator
3:58 p.m.
--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(a)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(a)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(a)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(a)redhat.com</a>&gt;=
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-en... =
class=3D"">https://bugzilla.redhat.com/enter_bug.cgi?product...
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(a)1und1.de</a>&gt;</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(a)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--
4:32 p.m.
This is a multi-part message in MIME format.
--------------74EE177BC08218117BD6CB3D
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Hello, thank you for fast response.
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.
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.
I'll just opened an RFE https://bugzilla.redhat.com/show_bug.cgi?id=1475382
Best regards,
Ladislav Humenik
On 26.07.2017 15:58, Michal Skrivanek wrote:
> On 26 Jul 2017, at 16:50, Jakub Niedermertl <jniederm(a)redhat.com
> <mailto:jniederm@redhat.com>> wrote:
>
> Hello Ladislav,
>
> the function computing size of default maximum memory size is
> currently not configurable from DB.
>
> If you want it to be so please feel free to file an RFE [1].
>
> [1]: https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine
>
> Best regards,
> Jakub
>
> On Wed, Jul 26, 2017 at 1:59 PM, Ladislav Humenik
> <ladislav.humenik(a)1und1.de <mailto:ladislav.humenik@1und1.de>> wrote:
>
> Hallo, after engine update to 4.1.2 from 4.0.6 we have following bug
>
> *Your Future Description: *
>
> 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.
>
> During migration of engine 4.0 -> 4.1 all VM-like entities will
> get max memory = 4x memory.
>
> 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).
>
> *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
>
> *Template:
> *engine=# 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)
>
> *Created VM*
> - expected is mem_size_mb * VM64BitMaxMemorySizeInMB
> - we get mem_size_mb * 4 (default)
>
> *Engine: *engine=# 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)
>
> *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 “Blank” I think, Jakube?
That’s for the default case, you can change that any way you like for
the concrete VM you’re 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’s not anything you should need to
change.
Thanks,
michal
>
> Kind Regards,
> Ladislav Humenik, System administrator
>
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org <mailto:Users@ovirt.org>
> http://lists.ovirt.org/mailman/listinfo/users
--
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: ladislav.humenik(a)1und1.de | Web: www.1und1.de
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.
--------------74EE177BC08218117BD6CB3D
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
<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">h...
<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(a)redhat.com</a>&gt;
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...
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(a)1und1.de</a>&gt;</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(a)ovirt.org</a><br
class="">
<a class="moz-txt-link-freetext"
href="http://lists.ovirt.org/mailman/listinfo/users">http://...
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>
--------------74EE177BC08218117BD6CB3D--
7:01 p.m.
yes, max memory size is customizabe even for Blank template
On Wed, Jul 26, 2017 at 4:32 PM, Ladislav Humenik <ladislav.humenik(a)1und1.de
wrote:
> Hello, thank you for fast response.
>
> 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.
>
> 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.
>
> I'll just opened an RFE https://bugzilla.redhat.com/
> show_bug.cgi?id=1475382
>
> Best regards,
> Ladislav Humenik
>
>
> On 26.07.2017 15:58, Michal Skrivanek wrote:
>
>
> On 26 Jul 2017, at 16:50, Jakub Niedermertl <jniederm(a)redhat.com wrote:
>
> Hello Ladislav,
>
> the function computing size of default maximum memory size is currently
> not configurable from DB.
>
> If you want it to be so please feel free to file an RFE [1].
>
> [1]: https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine
>
> Best regards,
> Jakub
>
> On Wed, Jul 26, 2017 at 1:59 PM, Ladislav Humenik <
> ladislav.humenik(a)1und1.de wrote:
>
>> Hallo, after engine update to 4.1.2 from 4.0.6 we have following bug
>>
>> *Your Future Description: *
>>
>> 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.
>>
>> During migration of engine 4.0 -> 4.1 all VM-like entities will get max
>> memory = 4x memory.
>>
>> 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).
>>
>> *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
>>
>> *Template:
>> *engine=# 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)
>>
>> *Created VM*
>> - expected is mem_size_mb * VM64BitMaxMemorySizeInMB
>> - we get mem_size_mb * 4 (default)
>>
>> *Engine: *engine=# 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)
>>
>> *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
> “Blank” I think, Jakube?
> That’s for the default case, you can change that any way you like for the
> concrete VM you’re 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’s not anything you should need to
> change.
>
> Thanks,
> michal
>
>
>> Kind Regards,
>> Ladislav Humenik, System administrator
>>
>>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
>
> --
> 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 <+49%20721%20913748361>
> E-Mail: ladislav.humenik(a)1und1.de | Web: www.1und1.de
>
> 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.
>
>
10:03 a.m.
On 26 Jul 2017, at 14:59, Ladislav Humenik
<ladislav.humenik(a)1und1.de> wrote:
Hallo, after engine update to 4.1.2 from 4.0.6 we have following bug
*Your Future Description: *
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.
During migration of engine 4.0 -> 4.1 all VM-like entities will get max memory = 4x
memory.
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).
*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
*Template:
*engine=# 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)
*Created VM*
- expected is mem_size_mb * VM64BitMaxMemorySizeInMB
- we get mem_size_mb * 4 (default)
*Engine: *engine=# 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)
*Question:*
It is possible to change this (default * 4) behavior in DB??
Hi,
no, not really, it’s just a UI-side default suggestion.
In API you supply it yourself in the request, any value you would want. It just limits the
max hotpluggable amount of memory
Thanks,
michal
Kind Regards,
Ladislav Humenik, System administrator
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
2729
days inactive
2730
days old
5 comments
3 participants
participants (3)
-
Jakub Niedermertl -
Ladislav Humenik -
Michal Skrivanek