On 30.09.2013 11:37, Daniel P. Berrange wrote:
> On Mon, Sep 30, 2013 at 11:30:11AM +0200, Michal Privoznik wrote:
>> The python binding to virNodeGetInfo API has this awful bug. The
>> amount of RAM the node has is reported in MiB instead of KiB as
>> we have documented in the struct virNodeInfo d
On Mon, Sep 30, 2013 at 11:30:11AM +0200, Michal Privoznik wrote:
> The python binding to virNodeGetInfo API has this awful bug. The
> amount of RAM the node has is reported in MiB instead of KiB as
> we have documented in the struct virNodeInfo description. The
> problem is, after we obtain the no
The python binding to virNodeGetInfo API has this awful bug. The
amount of RAM the node has is reported in MiB instead of KiB as
we have documented in the struct virNodeInfo description. The
problem is, after we obtain the nodeinfo the amount is shifted
left ten times (divided by 1024).
Signed-off