Fabian Ebner fe19840a56 api: create disks: always activate/update size when attaching existing volume ... For creation, activation and size update never triggered, because the passed in $conf is essentially the same as the creation $settings, so the disk was always detected to be the same as the "existing" one. But actually, all disks are new, so it makes sense to do it. For update, activation and size update nearly always triggered, because only the pending changes are passed in as $conf. The case where it didn't trigger is when the same pending change was made twice (there are cases where hotplug isn't done, but makes it even more unlikely). Signed-off-by: Fabian Ebner <f.ebner@proxmox.com>		2022-03-11 10:45:59 +01:00
..
Qemu	api: qga file-write: drop the check for base64	2022-02-10 16:27:57 +01:00
Makefile	buildsys: use $(MAKE) instead of make	2019-09-24 18:06:16 +02:00
Qemu.pm	api: create disks: always activate/update size when attaching existing volume	2022-03-11 10:45:59 +01:00