[libvirt] [PATCH v2 1/2] add nodeset='all' for interleave mode

sometimes we hoped that the memory of vm can be evenly distributed in all nodes according to interleave mode. But different hosts has different node number. So we add nodeset='all' for interleave mode. Signed-off-by: Peng Hao --- src/conf/numa_conf.c

[libvirt] [PATCH v2 2/2] add docs for interleave nodeset='all'

Signed-off-by: Peng Hao --- docs/formatdomain.html.in | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in index 1f12ab5..9aca921 100644 --- a/docs/formatdomain.html.in +++ b/docs/formatdomain.html.in @@ -1242,6 +1242,7

[libvirt] [PATCH] add nodeset='all' and default for interleave mode

For interleave mode,sometimes we want to allocate mmeory regularly in all nodes on the host. But different hosts has different node number. So we add nodeset='all' for interleave mode and if nodeset=NULL default nodeset is 'all' for interleave mode. Signed-off-by: Pen

[libvirt] [PATCH] qemu: monitor: fix unsafe monitor access

early, and then try to get mon->lock, it will block forerver cause mon->lock not released by qemuDomainObjExitMonitor. Signed-off-by: Wang Yechao Signed-off-by: Peng Hao --- src/qemu/THREADS.txt | 12 +- src/qemu/qemu_block.c| 5 +- src/qemu/qemu_domain.c

[libvirt] [PATCH v2] libvirt-python : PyObject memory leak

libvirt_virConnectDomainEventTunableCallback leak a PyObject. Signed-off-by: Peng Hao Signed-off-by: Wang Yechao --- libvirt-override.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libvirt-override.c b/libvirt-override.c index d746350..78a7f08 100644 --- a/libvirt

[libvirt] [PATCH] libvirt-python : PyObject memory leak

libvirt_virConnectDomainEventTunableCallback leak a PyObject Signed-off-by: Peng Hao Signed-off-by: Wang Yechao --- libvirt-override.c | 1 + 1 file changed, 1 insertion(+) diff --git a/libvirt-override.c b/libvirt-override.c index d746350..eab9b62 100644 --- a/libvirt-override.c +++ b

[libvirt] [PATCH RESEND] qemu: shared disks with cache=directsync should be safe for migration

From: Hao Peng At present shared disks can be migrated with either readonly or cache=none. But cache=directsync should be safe for migration, because both cache=directsync and cache=none don't use the host page cache, and cache=direct write through qemu block layer cache. Signed-off-by:

[libvirt] [PATCH] rpc : fix a access for null pointer

virNetSocketRemoveIOCallback get sock's ObjectLock and will call virNetSocketEventFree. virNetSocketEventFree may be free sock object and virNetSocketRemoveIOCallback will access a null pointer in release sock's ObjectLock. Signed-off-by: Liu Yun Signed-off-by: Peng Hao --

[libvirt] [PATCH] qemu: shared disks with cache=directsync should be safe for migration

From: Hao Peng At present shared disks can be migrated with either readonly or cache=none. But cache=directsync should be safe for migration, because both cache=directsync and cache=none don't use the host page cache, and cache=direct write through qemu block layer cache. Signed-off-by:

[libvirt] [PATCH] qemu: shared disks with cache=directsync should be safe for migration

From: Hao Peng At present shared disks can be migrated with either readonly or cache=none. But cache=directsync should be safe for migration, because both cache=directsync and cache=none don't use the host page cache, and cache=direct write through qemu block layer cache. Signed-off-by: