On 04/30/2014 10:35 AM, Vikas Kokare wrote:
> Juan,
>         Is there a workaround this issue? For eg, the absolute value of
> the statistic is correct, and hence the negative sign can be ignored. I
> am asking this, because the upgrade to higher versions of RHEVM (server
> and API) looks unlikely for us.
>
> -Vikas
>

No, there is no workaround, and the negative value isn't correct, you
can't just ignore the sign. The only alternative is to apply the patch.

If you are using oVirt then you can get the source, apply the patch, and
rebuild. Then you can replace the specific class, not everything. I
could assist you with that.

But I guess that you are using RHEV-M, and thus you will have a support
contract, if you modify the binaries you will end up with an unsupported
configuration. I would recommend you to open a support case with Red
Hat, so that they can try to give you a solution, maybe a hot fix, but I
can't guarantee that this is possible.

In the long term your best alternative is to upgrade.

>
> On Wed, Apr 30, 2014 at 1:32 PM, Juan Hernandez <jhernand@redhat.com

> <mailto:jhernand@redhat.com>> wrote:
>
>     On 04/30/2014 05:28 AM, Vikas Kokare wrote:
>     > The "memory.used" statistic on a virtual machine is returning a
>     negative
>     > value , ie.
>     >
>     > <statistic
>     >
>     href="/api/vms/260f8508-2bea-4202-9b93-f8f0dcddc334/statistics/b7499508-c1c3-32f0-8174-c1783e57bb08"
>     >
>     id="b7499508-c1c3-32f0-8174-c1783e57bb08"><name>memory.used</name><description>Memory
>     > used (agent)</description><values
>     >
>     type="INTEGER"><value><datum>*-2061584303*</datum></value></values><type>GAUGE</type><unit>BYTES</unit><vm
>     > href="/api/vms/260f8508-2bea-4202-9b93-f8f0dcddc334"
>     > id="260f8508-2bea-4202-9b93-f8f0dcddc334"/></statistic>
>     >
>     > by the RHEVM 3.2 ReST API.
>     > while, in the Web Administration Console, memory consumption for the
>     > same VM, shows a positive percentage value.
>     >
>     > Is this an issue with the ReST API?
>     >
>
>     Yes it is a known issue, and was solved in 3.3.4 and 3.4.0:
>
>     https://bugzilla.redhat.com/1068884
>

--
Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta
3ºD, 28016 Madrid, Spain
Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.