[one-users] Incorrect VM monitoring

[Antonio Carlos Salzvedel Furtado Junior]

Hi,

Thanks for the explanation. In my case, I think it would be a good idea to
adapt the probe.

Antonio Carlos Furtado

On Mon, May 14, 2012 at 5:22 AM, Ruben S. Montero
<rsmontero at opennebula.org>wrote:

> Hi
>
> In general you can take and tune the probes at var/remotes/im/kvm.d:
>
> 1.- CPU is gathered by kvm.rb using top. (free_cpu is associated to
> the idle parameter while used is total - free)
>
> 2.- In the same way, memory is obtained from virsh nodeinfo. If you
> plan to use ballooning, you need to adapt the probe. Currently it is
> getting the "Memory size" information
>
> Cheers
>
> Ruben
>
>
>
> On Thu, May 10, 2012 at 5:05 PM, Antonio Carlos Salzvedel Furtado
> Junior <acsfj08 at inf.ufpr.br> wrote:
> > I noticed it too when using KVM. In my case the CPU parameter was
> incorrect.
> > Let's say the Memory parameter was "correct", although it only prints the
> > maximum amount of memory that can be allocated to a VM. It does not
> consider
> > any information about the Virtio baloon driver, so I think this
> monitoring
> > is kind of pointless. If I go to the Qemu Monitor and inflate the baloon,
> > OpenNebula will still say that I have the same amount of memory.
> >
> >
> > In order to test the CPU parameter, I stressed the VM. As KVM treats the
> VMs
> > as normal processes, I just compared the OpenNebula results with the top
> > command. While top output the expected result, OpenNebula seemed to print
> > arbitrary numbers.
> >
> > Cordially,
> >
> > Antonio Carlos Furtado
> >
> >
> > On Thu, May 10, 2012 at 11:35 AM, Javier Alvarez <javier.alvarez at bsc.es>
> > wrote:
> >>
> >> Hello,
> >>
> >> I'm running OpenNebula over Xen in a single machine and everything works
> >> fine, the VMs boot correctly and I can access them through SSH without
> >> problems. The only thing is that the monitoring doesn't seem to be
> working
> >> well because 'onevm list' doesn't show any CPU nor Memory in the VMs.
> Only
> >> after a while, in the Memory column it appears 1020.3M, which anyways
> is not
> >> the real value. Also, /proc/meminfo and /proc/cpuinfo in the VMs show
> the
> >> expected values, as well as running 'xm list' in Dom0.
> >>
> >> Is not a big issue, but I'm afraid it could cause other problems in the
> >> future.
> >>
> >> Thank you,
> >>
> >> Javi
> >>
> >> --
> >> Javier Álvarez Cid-Fuentes
> >> Grid Computing and Clusters Group
> >> Barcelona Supercomputing Center (BSC-CNS)
> >> Tel. (+34) 93 413 72 46
> >>
> >>
> >> WARNING / LEGAL TEXT: This message is intended only for the use of the
> >> individual or entity to which it is addressed and may contain
> >> information which is privileged, confidential, proprietary, or exempt
> >> from disclosure under applicable law. If you are not the intended
> >> recipient or the person responsible for delivering the message to the
> >> intended recipient, you are strictly prohibited from disclosing,
> >> distributing, copying, or in any way using this message. If you have
> >> received this communication in error, please notify the sender and
> >> destroy and delete any copies you may have received.
> >>
> >> http://www.bsc.es/disclaimer
> >> _______________________________________________
> >> Users mailing list
> >> Users at lists.opennebula.org
> >> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
> >
> >
> >
> > _______________________________________________
> > Users mailing list
> > Users at lists.opennebula.org
> > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
> >
>
>
>
> --
> Ruben S. Montero, PhD
> Project co-Lead and Chief Architect
> OpenNebula - The Open Source Solution for Data Center Virtualization
> www.OpenNebula.org | rsmontero at opennebula.org | @OpenNebula
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20120514/5c5a0b8a/attachment-0003.htm>