Thomas Lamprecht b04ea58453 destroy_vm: allow to pass new config and lock instead ... This brings qemu more in line with containers, and it's nicer to allow passing the replacement config if we want to keep it, instead of setting a "memory: 128" config. Use that to lock it on removal before final deletion, and on legacy tar archive restore, in between old VM destruction and new restoration. Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>		2019-11-08 17:03:30 +01:00
..
API2	destroy_vm: allow to pass new config and lock instead	2019-11-08 17:03:30 +01:00
CLI	destroy_vm: allow to pass new config and lock instead	2019-11-08 17:03:30 +01:00
QemuServer	qm importdisk: tell user to what VM disk we actually imported	2019-10-29 19:11:21 +01:00
VZDump	backup: is IOThread comaptible: only check running VMs	2019-10-23 11:28:51 +02:00
Makefile	buildsys: use $(MAKE) instead of make	2019-09-24 18:06:16 +02:00
QemuConfig.pm	Fix #2171: vm_start: volid based statefiles were not activated	2019-10-17 19:20:32 +02:00
QemuMigrate.pm	fix typo in migration cleanup error message	2019-10-28 11:30:10 +01:00
QemuServer.pm	destroy_vm: allow to pass new config and lock instead	2019-11-08 17:03:30 +01:00
QMPClient.pm	QMPClient: add destructor	2019-10-30 10:36:51 +01:00