On Wed, Feb 08, 2012 at 16:35:57 +0800, Alex Jia wrote:
On 02/08/2012 02:59 PM, Daniel Veillard wrote:
> On Mon, Feb 06, 2012 at 03:21:21PM +0800, Daniel Veillard wrote:
>> We are now entering the freeze for libvirt-0.9.10
>> Hopefully all the API changes needed for that version are
>> already commited to git head.
> Okay I made an rc2 release with the python bindings fix (thanks !)
The python bindings work well for me on rhel, and unit test cases also
are fine except for
valgrind found a memory leak:
==21503== 112 (32 direct, 80 indirect) bytes in 1 blocks are definitely
lost in loss record 37 of 40
==21503== at 0x4A04A28: calloc (vg_replace_malloc.c:467)
==21503== by 0x4A8991: virAlloc (memory.c:101)
==21503== by 0x505A6C: x86DataCopy (cpu_x86.c:247)
==21503== by 0x507B34: x86Compute (cpu_x86.c:1225)
==21503== by 0x43103C: qemuBuildCommandLine (qemu_command.c:3561)
==21503== by 0x41C9F7: testCompareXMLToArgvHelper
(qemuxml2argvtest.c:183)
==21503== by 0x41E10D: virtTestRun (testutils.c:141)
==21503== by 0x41B942: mymain (qemuxml2argvtest.c:705)
==21503== by 0x41D7E7: virtTestMain (testutils.c:696)
This should be fixed by "qemu: Fix memory leak when building -cpu argument"
patch I've just sent.
Jirka