Hi, If I recall correctly, that was fixed in 3.4.x versions. If that was a one-time bug and you just need to reset the values, you can stop opennebula and edit the host_pool entry in the DB. The body column contains the complete XML you get with 'onehost show -x'.
Regards -- Carlos Martín, MSc Project Engineer OpenNebula - The Open-source Solution for Data Center Virtualization www.OpenNebula.org | cmar...@opennebula.org | @OpenNebula<http://twitter.com/opennebula><cmar...@opennebula.org> On Wed, Jun 13, 2012 at 4:06 AM, David <david1...@foxmail.com> wrote: > Hi, > I am using OpenNebula version is 3.2.1。 > The following strange usage values still exist in this release version， > and there is no virtual machine of the same name. > > I saw a virtual machine used memory value is 4G, but It takes up > belongs to host mem_usage value is 1G， this is very strange. > > ** > What is the solution In this version ? thanks! > > Regards. > > ------------------ 原始邮件 ------------------ > *发件人:* "Carlos Martín Sánch"<cmar...@opennebula.org>; > *发送时间:* 2012年6月12日(星期二) 晚上10:11 > *收件人:* "刘德伟"<david1...@foxmail.com>; ** > *抄送:* "users"<users@lists.opennebula.org>; ** > *主题:* Re: [one-users] Host resources statistical error! > > Hi, > > What OpenNebula version are you using? There was a bug in older versions > that sometimes caused these strange usage values. It was triggered when > several VMs had the same name. > > Regards > -- > Carlos Martín, MSc > Project Engineer > OpenNebula - The Open-source Solution for Data Center Virtualization > www.OpenNebula.org | cmar...@opennebula.org | > @OpenNebula<http://twitter.com/opennebula><cmar...@opennebula.org> > > > > On Mon, Jun 11, 2012 at 7:47 AM, 刘德伟 <david1...@foxmail.com> wrote: > >> Hi, >> [oneadmin@container-16 ~]$ onehost list >> ID NAME RVM TCPU FCPU ACPU TMEM FMEM AMEM >> STAT >> 9 vm-container-16 4 1600 1473 1200 16G 12.5G >> 19.4G on >> AMEM（19.4G） greater than TMEM（16G）， this phenomenon often appear in >> other environment. >> It leads to obtain XML data was wrong. >> <HOST_SHARE> >> <DISK_USAGE>0</DISK_USAGE> >> <MEM_USAGE>-32243712</MEM_USAGE> >> <CPU_USAGE>0</CPU_USAGE> >> <MAX_DISK>0</MAX_DISK> >> <MAX_MEM>8046480</MAX_MEM> >> <MAX_CPU>400</MAX_CPU> >> <FREE_DISK>0</FREE_DISK> >> <FREE_MEM>7633692</FREE_MEM> >> <FREE_CPU>399</FREE_CPU> >> <USED_DISK>0</USED_DISK> >> <USED_MEM>412788</USED_MEM> >> <USED_CPU>0</USED_CPU> >> <RUNNING_VMS>0</RUNNING_VMS> >> </HOST_SHARE> >> MEM_USAGE become negative ， at the same time the virtual machine >> scheduling is affected, also we call to XML-RPC have an effect. >> What was the reason for the cases above ? >> >> regards! >> David. >> >> >> _______________________________________________ >> Users mailing list >> Users@lists.opennebula.org >> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org >> >> > ** >
_______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
