2012/4/1 Maxim Sditanov feni...@rambler.ru
2012/4/1 Feniks Gordon Freeman feni...@rambler.ru
2012/4/1 Feniks Gordon Freeman feni...@rambler.ru
2012/4/1 Laine Stump la...@laine.org
On 03/31/2012 07:56 AM, Daniel Veillard wrote:
I just made the second release candidate
Fix-typos-and-spacing-in-messages.patch
Description: Binary data
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
On 03/29/2012 10:20 PM, Guannan Ren wrote:
On 03/29/2012 08:14 PM, Martin Kletzander wrote:
- fix hard-coded options into real options (e.g. commit 65449e)
- fix some env_* and util* code (functions duplicated with different
behavior)
- fix or remove harmful and pointless code (at this
Currently, we use migrate to dump guest's memory. There is one
restriction in migrate command: the device's status should be
stored in qemu because the device's status should be passed to
target machine.
If we passthrough a host device to guest, the device's status
is stored in the real device.
---
src/qemu/qemu_domain.c |1 +
src/qemu/qemu_domain.h |1 +
src/qemu/qemu_driver.c | 42 --
3 files changed, 42 insertions(+), 2 deletions(-)
diff --git a/src/qemu/qemu_domain.c b/src/qemu/qemu_domain.c
index 69d9e6e..e3a668a 100644
---
This patch introduces the API to use qemu's new monitor command
dump-guest-memory
---
src/qemu/qemu_monitor.c | 32
src/qemu/qemu_monitor.h | 13 +++
src/qemu/qemu_monitor_json.c | 42 +
src/qemu/qemu_monitor_json.h |7
https://bugzilla.redhat.com/show_bug.cgi?id=808979
The leak is really in virProcessInfoGetAffinity, as shown in the
valgrind output given in the above bug report - it calls CPU_ALLOC(),
but then fails to call CPU_FREE().
This leak has existed in every version of libvirt since 0.7.5.
---
At 04/02/2012 01:33 PM, Laine Stump Wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=808979
The leak is really in virProcessInfoGetAffinity, as shown in the
valgrind output given in the above bug report - it calls CPU_ALLOC(),
but then fails to call CPU_FREE().
This leak has existed in
