Fabian Ebner 0d2db08414 prefer storage_check_enabled over storage_check_node ... storage_check_enabled simply checks for the 'disable' option and then calls storage_check_node. While not strictly necessary for a second call where only the storage differs, e.g. in case of clone, it is more future-proof: if support for a target storage is added at some point, it might be easy to miss adapting the call. For the migration checks, the situation is improved by now always catching disabled (target) storages. Signed-off-by: Fabian Ebner <f.ebner@proxmox.com>		2021-06-21 11:17:48 +02:00
..
API2	prefer storage_check_enabled over storage_check_node	2021-06-21 11:17:48 +02:00
CLI	qm: assume correct VNC setup in 'vncproxy', disallow passwordless	2021-05-28 11:31:15 +02:00
QemuServer	fix bootdisk_size for new bootorder config scheme	2021-04-29 16:15:33 +02:00
VZDump	vzdump: add master key support	2021-06-02 16:49:00 +02:00
Makefile	buildsys: use $(MAKE) instead of make	2019-09-24 18:06:16 +02:00
QemuConfig.pm	snapshot: set migration caps before savevm-start	2021-03-16 20:44:51 +01:00
QemuMigrate.pm	prefer storage_check_enabled over storage_check_node	2021-06-21 11:17:48 +02:00
QemuServer.pm	prefer storage_check_enabled over storage_check_node	2021-06-21 11:17:48 +02:00
QMPClient.pm	tree wide cleanups	2020-10-16 18:03:32 +02:00