summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMichal Privoznik <mprivozn@redhat.com>2013-09-30 11:23:08 +0200
committerMichal Privoznik <mprivozn@redhat.com>2013-09-30 11:42:52 +0200
commitbc116872291690bc18e475d51a65748122ddec44 (patch)
tree947e09acfad367d756ee7485e0762061a624f04a
parent357df252fb58cb8d34bdc5df3bc74db8ff923bb2 (diff)
downloadlibvirt-python-v8-bc116872291690bc18e475d51a65748122ddec44.tar.gz
libvirt-python-v8-bc116872291690bc18e475d51a65748122ddec44.tar.xz
libvirt-python-v8-bc116872291690bc18e475d51a65748122ddec44.zip
python: Document virNodeGetInfo bug
The memory size in virNodeGetInfo python API binding is reported in MiB instead of KiB (like we have in C struct). However, there already might be applications out there relying on this inconsistence so we can't simply fix it. Document this sad fact as known bug.
-rw-r--r--libvirt-override-api.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/libvirt-override-api.xml b/libvirt-override-api.xml
index 1bceb05..337d0a0 100644
--- a/libvirt-override-api.xml
+++ b/libvirt-override-api.xml
@@ -100,7 +100,7 @@
<arg name='flags' type='unsigned int' info='flags, currently unused, pass 0.'/>
</function>
<function name='virNodeGetInfo' file='python'>
- <info>Extract hardware information about the Node.</info>
+ <info>Extract hardware information about the Node. Note that the memory size is reported in MiB instead of KiB.</info>
<return type='char *' info='the list of information or None in case of error'/>
<arg name='conn' type='virConnectPtr' info='pointer to the hypervisor connection'/>
</function>