There is no benefit in providing two ways of connecting to vz driver: by connecting via daemon and directly from client. Both ways finally come to a host where vz daemon sits. Always connecting via daemon allows us to have a single list of domains and share it among all connections. Since v1: removed patch "z: remove close callback implementations" building fixed close callback functions are added to libvirt_private.syms reworked not to lose event subscribers when connections drop Maxim Nestratov (10): virsh: report when vz driver is compiled vz: change the order of capabilities reported vz: remove drivername field from vzConn structure vz: add Hypervisor prefix to vz and parallels Driver structures vz: build driver as module and don't register it on client's side vz: introduce new vzDriver lockable structure and use it vz: implement connectGetSysinfo hypervisor callback vz: remove vzDriverLock/Unlock function vz: minor cleanup vz: change vzConnectIsAlive behavior daemon/Makefile.am | 4 + daemon/libvirtd.c | 9 ++ src/Makefile.am | 20 ++- src/libvirt.c | 7 - src/libvirt_private.syms | 6 + src/vz/vz_driver.c | 414 +++++++++++++++++++++++++++++------------------ src/vz/vz_sdk.c | 211 ++++++++++++------------ src/vz/vz_sdk.h | 30 ++-- src/vz/vz_utils.c | 32 ++-- src/vz/vz_utils.h | 33 +++- tools/virsh.c | 3 + 11 files changed, 452 insertions(+), 317 deletions(-) -- 2.4.3 -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list