[libvirt] [PATCH] qemuProcess: update hostdevs before connectting qemu monitor

. This patch fixs that by moving qemuHostdevUpdateActiveDomainDevices before qemuConnectMonitor. Signed-off-by: Wu Zongyong --- src/qemu/qemu_process.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/qemu/qemu_process.c b/src/qemu/qemu_process.c index f9a01da..d187271

[libvirt] [PATCH] virhostdev: Fix PCI devices are still attatched to stub driver bug

driver + attached to the stub driver. Moreover, we set orignal states of PCI devices when build PCI devices list in virHostdevGetPCIHostDeviceList if states has been set in struct virDomainHostdevDefPtr. Signed-off-by: Wu Zongyong --- src/util/virhostdev.c | 20 ++-- 1 file changed

[libvirt] Why does vnc show blackscreen after using mstsc to connect to a windows vm with a nvidia gpu passtrough

Hi, As the title says, VNC inside a windows virtual machine doesn’t work after I try to use mstsc to access the vm with a gpu passthrough. It seems that the scenario is normal, but could someone tell me something deeply about the reason why vnc shows blackscreen? Thanks. -- libvir-list

[libvirt] [PATCH v3 0/3] nodedev: update caps before quering nodedev infos

to manually update devices' capabilities each time before nodedev driver interfaces invoked. Wu Zongyong (3): v2->v3: 1. split a single patch to three part 2. fix memory leak and lock problems 3. update caps before invoking nodedev driver interfaces (refer to patch 3/3) nodedev:

[libvirt] [PATCH 3/3] nodedev: update caps before invoking nodedev driver interfaces

Some capabilities of node devices rely on what driver they bound to, and therefore, these capabilities may change when the driver change. So, it is necessary to manually update devices' capabilities each time before nodedev driver interfaces invoked. Signed-off-by: Wu Zongyong <cord

[libvirt] [PATCH 1/3] nodedev: add macro guard to node_device_udev header file

Signed-off-by: Wu Zongyong <cordius...@huawei.com> --- src/node_device/node_device_udev.h | 15 ++- 1 file changed, 10 insertions(+), 5 deletions(-) diff --git a/src/node_device/node_device_udev.h b/src/node_device/node_device_udev.h index f15e520..300f57e 100644 ---

[libvirt] [PATCH 2/3] nodedev: update mdev_types caps before dumpxml

consistent with real status of the device. Signed-off-by: Wu Zongyong <cordius...@huawei.com> --- src/node_device/node_device_linux_sysfs.c | 22 ++ src/node_device/node_device_udev.c| 37 ++- src/node_device/node_device_udev.h| 3 +++ 3

[libvirt] [PATCH v2] nodedev: update mdev_types caps before dumpxml

consistent with real status of the device. Signed-off-by: Wu Zongyong <cordius...@huawei.com> --- v2: - fix mistakes pointed out by Erik src/node_device/node_device_linux_sysfs.c | 21 + src/node_device/node_device_udev.c| 29 + src/node_

[libvirt] [PATCH] nodedev: update mdev_types caps before dumpxml

In current implemention, mdev_types caps keep constant all the time. But, it is possible that a device capable of mdev_types sometime(for example:bind to proper driver) and incapable of mdev_types at other times(for example: unbind from its driver). We should keep the info of xml dumped out

[libvirt] [PATCH] nodedev: update mdev_types caps before dumpxml

Wu Zongyong (1): nodedev: update mdev_types caps before dumpxml src/node_device/node_device_linux_sysfs.c | 42 +++ src/node_device/node_device_udev.c| 11 ++-- src/node_device/node_device_udev.h| 8 ++ 3 files changed, 59 insertions(+), 2

[libvirt] [PATCH] Fix the incorrect memory freeing which will result in crash

The number of elements in new_params is equal to the length of info, instead of nparams, so it's wrong to free new_params using nparams. Signed-off-by: Wu Zongyong <wuzon...@mail.ustc.edu.cn> --- libvirt-override.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff