Hi, I'm interested in the very same question.
Additionally I don't see any way how this would break backwards compatibility. In contrary, in 3.4 some other values in the API change in a not backward compatible way, which actually do what they are supposed to do, so even if it would break compatibility this wouldn't clearly be a "no go" as it is done in other parts of the API too. In case you don't know which values I mean: I talk about the JSON implementation. I think the old value is pretty useless and needs to be fixed. So I don't see how a fix to this value should break any compatibility. I would be very interested in seeing the actual code which relies on negative values of consumed ram inside a vm. What would you do with it? Am 12.02.2014 18:31, schrieb René Koch: > I just had a look at the bugzilla report and the RHEV documentation > which says "Current memory in bytes used by the virtual machine.". > So this means, the reported values are totally useless for monitoring > memory usage of a virtual machine if KSM is active. I would expect to > get the memory usage of a virtual machine and not how much memory is > consumed on the hypervisor (this is pretty useless information for me). > > Is it planned to report the memory usage in a virtual machine in the API > as well? -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users