[libvirt] [PATCH v3 0/6] vz: change vz driver to be stateful driver and other enhancements

Maxim Nestratov mnestratov at virtuozzo.com
Tue Apr 12 18:31:43 UTC 2016


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

Since v2:
 removed "vz: change vzConnectIsAlive behavior"
 addressed mostly all comments on previous series
 changed "vz: build driver as module and don't register it on client's side"

Maxim Nestratov (6):
  vz: build driver as module and don't register it on client's side
  vz: introduce new vzDriver lockable structure and use it
  vz: lock driver when a new domain is created in
    prlsdkNewDomainByHandle
  vz: implement connectGetSysinfo hypervisor callback
  vz: remove vzDriverLock/Unlock function
  vz: minor cleanup

 daemon/Makefile.am       |   4 +
 daemon/libvirtd.c        |   9 ++
 src/Makefile.am          |  19 ++-
 src/libvirt.c            |   7 -
 src/libvirt_private.syms |   7 +
 src/vz/vz_driver.c       | 384 +++++++++++++++++++++++++++++------------------
 src/vz/vz_sdk.c          | 211 +++++++++++++-------------
 src/vz/vz_sdk.h          |  30 ++--
 src/vz/vz_utils.c        |  27 ++--
 src/vz/vz_utils.h        |  34 +++--
 10 files changed, 431 insertions(+), 301 deletions(-)

-- 
2.4.3




More information about the libvir-list mailing list