5 Commits

Author	SHA1	Message	Date
Dominik Csapak	28831e1014	add new tests for 'runningmachine' and rollback ... Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>	2018-09-17 15:49:31 +02:00
Dominik Csapak	c6737ef18b	ensure correct machine type gets saved on snapshot ... instead of overwriting the 'machine' config in the snapshot, use its own 'runningmachine' config only for the snapshot this way, we do not lose the machine type if it was explicitely set during the snapshot, but deleted afterwards we also have to adapt the tests for this Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>	2018-09-17 15:48:05 +02:00
Fabian Grünbichler	d47ea4d05a	tests: fix broken snapshot delete tests ... these broke when the additional "snapshot-delete" lock was introduced Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>	2017-05-17 13:58:18 +02:00
Fabian Grünbichler	b2c9558da8	Rework snapshot code, has_feature ... Drop snapshot_create, snapshot_delete and snapshot_rollback in favour of PVE::AbstractConfig. Qemu-specific parts are implemented in __snapshot_XX methods in PVE::QemuConfig. has_feature is made an implementation of the abstract has_feature, and thus moves to PVE::QemuConfig. Note: a new hook method needed to be introduced to be called before creating a volume snapshot, after creating a volume snapshot, and after unfreezing the guestfs after creating a volume snapshot. The base method in PVE::AbstractConfig is a noop, the implemention in PVE::QemuConfig runs the necessary Qemu monitor commands.	2016-03-08 11:42:37 +01:00
Fabian Grünbichler	a157d0fd17	Add regression tests for snapshotting ... these are modelled after the existing snapshot tests for LXC and should serve as a baseline for refactoring the Qemu snapshot code using PVE::AbstractConfig	2016-03-04 11:23:23 +01:00