Patch 1 relaxes the requirement of PID != 0 in the locking code.
danpb and I discussed this on IRC:
danpb: jimfehlig: it wouldn't be the end of the world if
you leave pid as 0
danpb: jimfehlig: it'd just loose some safety sanity check
in that scenario
Patch 2 introduces a config file for the libxl driver, with the lone
config entry 'autoballoon'. I thought this would make review easier,
vs adding all the config file support in patch 3, which is fairly
large as is.
Jim Fehlig (3):
locking: relax PID requirement
libxl: Introduce configuration file for libxl driver
libxl: provide integration with lock manager
libvirt.spec.in | 8 ++++
src/Makefile.am | 36 ++++++++++++++++-
src/libxl/libvirtd_libxl.aug | 44 +++++++++++++++++++++
src/libxl/libxl.conf | 22 +++++++++++
src/libxl/libxl_conf.c | 75 +++++++++++++++++++++++++++++++++---
src/libxl/libxl_conf.h | 11 ++++++
src/libxl/libxl_domain.c | 47 +++++++++++++++++++++-
src/libxl/libxl_domain.h | 1 +
src/libxl/libxl_driver.c | 34 ++++++++++++++++
src/libxl/libxl_migration.c | 6 +++
src/libxl/test_libvirtd_libxl.aug.in | 6 +++
src/locking/lock_daemon.c | 2 +-
src/locking/lock_daemon_dispatch.c | 49 +++++++----------------
src/locking/lock_driver_lockd.c | 7 +---
14 files changed, 298 insertions(+), 50 deletions(-)
create mode 100644 src/libxl/libvirtd_libxl.aug
create mode 100644 src/libxl/libxl.conf
create mode 100644 src/libxl/test_libvirtd_libxl.aug.in
--
1.8.4.5