Jim Fehlig 0c710a37ea libxl: resume lock process after failed migration ... During migration, the lock process is paused in the perform phase but not resumed if there is a subsequent failure, leaving the locked resource unprotected. The perform phase itself can fail, in which case the lock process should be resumed before returning from perform. The finish phase could also fail on the destination host, in which case the migration is canceled in the confirm phase and the VM is resumed. The lock process needs to be resumed there as well. Signed-off-by: Jim Fehlig <jfehlig@suse.com>		2018-01-25 09:22:14 -07:00
..
libvirtd_libxl.aug
libxl_capabilities.c	cpu: Drop unused parameter from cpuDecode	2017-10-16 09:21:52 +02:00
libxl_capabilities.h
libxl_conf.c	libxl: add support for multiple IP addresses	2017-12-08 13:55:07 -07:00
libxl_conf.h
libxl_domain.c	libxl: add support for multiple IP addresses	2017-12-08 13:55:07 -07:00
libxl_domain.h	Remove backslash alignment attempts	2017-11-03 13:24:12 +01:00
libxl_driver.c	libxl: mark domain0 as persistent	2017-12-15 15:25:01 -07:00
libxl_driver.h
libxl_logger.c
libxl_logger.h
libxl_migration.c	libxl: resume lock process after failed migration	2018-01-25 09:22:14 -07:00
libxl_migration.h	Remove backslash alignment attempts	2017-11-03 13:24:12 +01:00
libxl.conf
test_libvirtd_libxl.aug.in