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.
Maxim Nestratov (11):
virsh: report when vz driver is compiled
vz: change the order of capabilities reported
vz: remove drivername field from vzConn structure
vz: build driver as module and don't register it on client's side
vz: pass vzConnPtr to prlsdkXxx functions instead of virConnectPtr
vz: make vzConn structure be a new lockable object and use it
vz: implement connectGetSysinfo hypervisor callback
vz: remove close callback implementations
vz: remove vzDriverLock/Unlock function
vz: minor cleanup
vz: change vzConnectIsAlive behavior
daemon/Makefile.am | 4 +
daemon/libvirtd.c | 9 +
src/Makefile.am | 21 ++-
src/libvirt.c | 7 -
src/vz/vz_driver.c | 479 ++++++++++++++++++++++++++++++-----------------------
src/vz/vz_sdk.c | 36 ++--
src/vz/vz_sdk.h | 6 +-
src/vz/vz_utils.c | 18 +-
src/vz/vz_utils.h | 15 +-
tools/virsh.c | 3 +
10 files changed, 341 insertions(+), 257 deletions(-)
--
2.4.3