From: Hannes Duerr <h.duerr@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH qemu-server/storage v4 0/2] fix #1611: implement import of base-images for LVM-thin Storage
Date: Tue, 19 Dec 2023 15:03:04 +0100 [thread overview]
Message-ID: <20231219140306.188937-1-h.duerr@proxmox.com> (raw)
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
next reply other threads:[~2023-12-19 14:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 14:03 Hannes Duerr [this message]
2023-12-19 14:03 ` [pve-devel] [PATCH qemu-server v4 1/2] migration: secure and use source volume names for deactivation Hannes Duerr
2024-01-30 9:42 ` [pve-devel] applied: " Fabian Grünbichler
2023-12-19 14:03 ` [pve-devel] [PATCH pve-storage v4 2/2] fix #1611: implement import of base-images for LVM-thin Storage Hannes Duerr
2023-12-19 14:10 ` Lukas Wagner
2024-01-30 10:00 ` Fabian Grünbichler
2024-04-10 8:55 ` Hannes Dürr
2024-04-18 13:24 ` [pve-devel] applied: " Fabian Grünbichler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231219140306.188937-1-h.duerr@proxmox.com \
--to=h.duerr@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox