if a base-image is to be migrated to a lvm-thin storage, a new vm-image is allocated on the target side, then the data is written and afterwards the image is converted to a base-image
Changes in V2: * restructure and remove duplicaiton * fix deactivation of volumes after migration Changes in V3: * fix Nits * remove unnecessary oldname override * deactivate not only offline volumes, but all Changes in V4: * remove debug stuff * remove unnecessary key in $self qemu-server: Hannes Duerr (1): migration: secure and use source volume names for deactivation PVE/QemuMigrate.pm | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) pve-storage: Hannes Duerr (1): fix #1611: implement import of base-images for LVM-thin Storage src/PVE/Storage/LvmThinPlugin.pm | 50 ++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) Summary over all repositories: 2 files changed, 53 insertions(+), 0 deletions(-) -- Generated by git-murpp 0.5.0 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
