[Users] oVirt warning about memory usage
Hi, just seen a memory usage warning in oVirt's Admin Interface saying the available memory is below threshold of 1024MB - however - when I checked the host, it had still 20GB left ? See screenshot. Alex
----- Original Message -----
From: "Alex Leonhardt" <alex.tuxx@gmail.com> To: "oVirt Mailing List" <users@ovirt.org> Sent: Monday, January 7, 2013 11:18:27 AM Subject: [Users] oVirt warning about memory usage
Hi,
just seen a memory usage warning in oVirt's Admin Interface saying the available memory is below threshold of 1024MB - however - when I checked the host, it had still 20GB left ?
Did you note that the number reporting in the warning has a negative sign ? Seems to me as a bug
See screenshot.
Alex
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
This is a multi-part message in MIME format. --------------090700000505010708000402 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 01/07/2013 06:18 AM, Alex Leonhardt wrote:
Hi,
just seen a memory usage warning in oVirt's Admin Interface saying the available memory is below threshold of 1024MB - however - when I checked the host, it had still 20GB left ?
See screenshot.
Alex
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
The message is happening due to "memAvailable" statistic coming from vdsm. The memAvailable field can be negative and considers a set of values from different sources to compose its result (free memory, cached memory, resident set size from qemu processes, committed memory from running vms and host reserved memory --------------090700000505010708000402 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> <div class="moz-cite-prefix">On 01/07/2013 06:18 AM, Alex Leonhardt wrote:<br> </div> <blockquote cite="mid:CAH4_GUutbaY-LoDUfc+LMiP2E85tfGQqU9vkBg2ZrN_Sf1B++g@mail.gmail.com" type="cite"> <div dir="ltr"> <div>Hi,<br> <br> just seen a memory usage warning in oVirt's Admin Interface saying the available memory is below threshold of 1024MB - however - when I checked the host, it had still 20GB left ? <br> <br> </div> See screenshot. <br> <br> Alex<br> <br> </div> <br> <fieldset class="mimeAttachmentHeader"></fieldset> <br> <pre wrap="">_______________________________________________ Users mailing list <a class="moz-txt-link-abbreviated" href="mailto:Users@ovirt.org">Users@ovirt.org</a> <a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a> </pre> </blockquote> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> <pre class="caseCommentStyle publicComment" style="margin: 0px; padding: 0px; line-height: 14px; white-space: pre-wrap; font-size: 12px; color: rgb(0, 0, 0); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;">The message is happening due to "memAvailable" statistic coming from vdsm. The memAvailable field can be negative and considers a set of values from different sources to compose its result (free memory, cached memory, resident set size from qemu processes, committed memory from running vms and host reserved memory</pre> </body> </html> --------------090700000505010708000402--
thanks, yep noticed it has a negative value - Amador, does that mean the host is overcommitting by 18 G of avail physical memory although 20 G of phys memory is still free ? Alex 2013/1/7 Amador Pahim <apahim@redhat.com>
On 01/07/2013 06:18 AM, Alex Leonhardt wrote:
Hi,
just seen a memory usage warning in oVirt's Admin Interface saying the available memory is below threshold of 1024MB - however - when I checked the host, it had still 20GB left ?
See screenshot.
Alex
_______________________________________________ Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
The message is happening due to "memAvailable" statistic coming from vdsm. The memAvailable field can be negative and considers a set of values from different sources to compose its result (free memory, cached memory, resident set size from qemu processes, committed memory from running vms and host reserved memory
This is a multi-part message in MIME format. --------------080502050502000507060404 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 01/08/2013 11:38 AM, Alex Leonhardt wrote:
thanks, yep noticed it has a negative value -
Amador, does that mean the host is overcommitting by 18 G of avail physical memory although 20 G of phys memory is still free ?
memAvailable maps the worst case to the Host. It means: considering your current state, to assure the "Physical Memory Guaranteed" for all running VMs, you need 18GB of additional RAM. This is the consequence of enabling overcommit policy. memAvailable = FREE_OR_CACHED + RESIDENT - memCommitted - Host Reserved Memory Where: FREE_OR_CACHED: from /proc/meminfo RESIDENT: RSS value (2nd. field in /proc/<PID>/statm) from all running VMs processes. memCommitted --> Physical Memory Guaranteed + Guest Overhead (default 65MB) from running VMs. *Notice that memAvailable does not considers KSM work.
Alex
2013/1/7 Amador Pahim <apahim@redhat.com <mailto:apahim@redhat.com>>
On 01/07/2013 06:18 AM, Alex Leonhardt wrote:
Hi,
just seen a memory usage warning in oVirt's Admin Interface saying the available memory is below threshold of 1024MB - however - when I checked the host, it had still 20GB left ?
See screenshot.
Alex
_______________________________________________ Users mailing list Users@ovirt.org <mailto:Users@ovirt.org> http://lists.ovirt.org/mailman/listinfo/users
The message is happening due to "memAvailable" statistic coming from vdsm. The memAvailable field can be negative and considers a set of values from different sources to compose its result (free memory, cached memory, resident set size from qemu processes, committed memory from running vms and host reserved memory
--------------080502050502000507060404 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> <div class="moz-cite-prefix">On 01/08/2013 11:38 AM, Alex Leonhardt wrote:<br> </div> <blockquote cite="mid:CAH4_GUtdRR611ePSun8zLyoGumXmeZnTsinK1O-B5Vz1AxUE8Q@mail.gmail.com" type="cite"> <div dir="ltr">thanks, yep noticed it has a negative value - <br> <br> Amador, does that mean the host is overcommitting by 18 G of avail physical memory although 20 G of phys memory is still free ?<br> </div> </blockquote> <br> memAvailable maps the worst case to the Host.<br> It means: considering your current state, to assure the "Physical Memory Guaranteed" for all running VMs, you need 18GB of additional RAM. This is the consequence of enabling overcommit policy. <br> <br> memAvailable = FREE_OR_CACHED + RESIDENT - memCommitted - Host Reserved Memory<br> <br> Where:<br> FREE_OR_CACHED: from /proc/meminfo<br> RESIDENT: RSS value (2nd. field in /proc/<PID>/statm) from all running VMs processes.<br> memCommitted --> Physical Memory Guaranteed + Guest Overhead (default 65MB) from running VMs.<br> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> <br> *Notice that memAvailable does not considers KSM work.<br> <br> <blockquote cite="mid:CAH4_GUtdRR611ePSun8zLyoGumXmeZnTsinK1O-B5Vz1AxUE8Q@mail.gmail.com" type="cite"> <div dir="ltr"><br> Alex<br> <br> </div> <div class="gmail_extra"><br> <br> <div class="gmail_quote">2013/1/7 Amador Pahim <span dir="ltr"><<a moz-do-not-send="true" href="mailto:apahim@redhat.com" target="_blank">apahim@redhat.com</a>></span><br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div bgcolor="#FFFFFF" text="#000000"> <div> <div class="h5"> <div>On 01/07/2013 06:18 AM, Alex Leonhardt wrote:<br> </div> </div> </div> <blockquote type="cite"> <div> <div class="h5"> <div dir="ltr"> <div>Hi,<br> <br> just seen a memory usage warning in oVirt's Admin Interface saying the available memory is below threshold of 1024MB - however - when I checked the host, it had still 20GB left ? <br> <br> </div> See screenshot. <br> <br> Alex<br> <br> </div> <br> <fieldset></fieldset> <br> </div> </div> <div class="im"> <pre>_______________________________________________ Users mailing list <a moz-do-not-send="true" href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a> <a moz-do-not-send="true" href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a> </pre> </div> </blockquote> <pre style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:start;font-style:normal;font-weight:normal;padding:0px;line-height:14px;text-transform:none;font-size:12px;white-space:pre-wrap;margin:0px;word-spacing:0px">The message is happening due to "memAvailable" statistic coming from vdsm. The memAvailable field can be negative and considers a set of values from different sources to compose its result (free memory, cached memory, resident set size from qemu processes, committed memory from running vms and host reserved memory</pre> </div> </blockquote> </div> <br> </div> </blockquote> <br> </body> </html> --------------080502050502000507060404--
participants (3)
-
Alex Leonhardt -
Amador Pahim -
Eli Mesika