From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH-SERIES v3 pve-storage/qemu-server/pve-qemu] add external qcow2 snapshot support
Date: Thu, 9 Jan 2025 15:13:14 +0100 (CET) [thread overview]
Message-ID: <1841615375.1037.1736431994704@webmail.proxmox.com> (raw)
In-Reply-To: <mailman.214.1734340397.332.pve-devel@lists.proxmox.com>
> Alexandre Derumier via pve-devel <pve-devel@lists.proxmox.com> hat am 16.12.2024 10:12 CET geschrieben:
> This patch series implement qcow2 external snapshot support for files && lvm volumes
>
> The current internal qcow2 snapshots have bad write performance because no metadatas can be preallocated.
>
> This is particulary visible on a shared filesystem like ocfs2 or gfs2.
>
> Also other bugs are freeze/lock reported by users since years on snapshots delete on nfs
> (The disk access seem to be frozen during all the delete duration)
>
> This also open doors for remote snapshot export-import for storage replication.
a few high level remarks:
- I am not sure whether we want to/can switch over to blockdev on the fly (i.e., without some sort of opt-in phase to iron out kinks). what about upgrades with running VMs? I guess some sort of flag and per-VM switching would be a better plan..
- I am also not sure whether we want to mix and match internal and external snapshots, we probably should require a storage to use it or not at creation time and fix it, to allow us to keep the handling code from exploding complexity-wise..
- if you see a way to name the block graph nodes in a deterministic fashion (i.e., have a 1:1 mapping between snapshot and block graph node name) that would be wonderful, else we'd have to find another way to improve the lookup there..
- the relevant commits and code would really benefit from a summary of the design/semantics, it's not easy to reconstruct this from the code alone
- some tests would be great as well, both to verify that the code actually behaves like we expect, and also to catch regressions when it is touched again in the future
- some performance numbers would also be great :)
-- internal vs external snapshots using the same underlying dir/fs
-- qcow2 vs qcow2 with snapshots vs raw on LVM using the same underlying disk
- did you verify the space consumption on the SAN side with the LVM plugin? would be interesting to know how it holds up in practice :)
I haven't done any real world testing yet since I expect that the delta for the next version won't be small either ;)
>
> Changelog v3:
> storage:
> - snapshots files now have the name of the snapshot, and "current" snapshot is the vm volname
> - allow only qcow2 format for base image for simplication
> - merge snapshot code in lvmplugin (qcow2 format auto enable snapshot)
> - the code is a lot more simple now
>
> qemu-server:
> - convertion -drive to modern -blockdev
> This is needed for blockdev-reopen, where we need to create && switch to snapshot files with same cache,aio,...
> This is also needed to live rename snapshot files (to keep volname for current snapshot)
> I have implemented && tested:
> - disk create,delete,resize,convert,drive_mirror, hotplug,unplug,nbd mirror,cdrom insert/eject
> - block protocol: file,block_device,rbd,nbd,glusterfs
> Note that it's currently incomplete:
> - proxmox backup/restore code need to be converted to blockdev, help is needed
> - iscsi:// path is not yet implemented (I'll look for the v4)
> - efi still in drive format (not blocking, but I'll look for v4)
>
> The live migration between -drive ---> --blockdev seem to work without breaking, and seem to be
> transparent for the guest ok, so I think we could try to target pve9 ?
>
>
>
> storage.cfg example:
>
> dir: local2
> path /var/liv/vz
> content snippets,vztmpl,backup,images,iso,rootdir
> snapext 1
>
> lvm:test
> vgname test
> content images
>
>
>
>
>
> pve-storage:
>
> Alexandre Derumier (3):
> qcow2: add external snapshot support
> lvmplugin: add qcow2 snapshot
> storage: vdisk_free: remove external snapshots
>
> src/PVE/Storage.pm | 18 ++-
> src/PVE/Storage/DirPlugin.pm | 1 +
> src/PVE/Storage/LVMPlugin.pm | 231 ++++++++++++++++++++++++++---
> src/PVE/Storage/Plugin.pm | 207 ++++++++++++++++++++++----
> src/test/run_test_zfspoolplugin.pl | 18 +++
> 5 files changed, 424 insertions(+), 51 deletions(-)
>
>
> Alexandre Derumier (11):
> blockdev: cmdline: convert drive to blockdev syntax
> blockdev: fix cfg2cmd tests
> blockdev : convert qemu_driveadd && qemu_drivedel
> blockdev: vm_devices_list : fix block-query
> blockdev: convert cdrom media eject/insert
> blockdev: block_resize: convert to blockdev
> blockdev: nbd_export: block-export-add : use drive-$id for nodename
> blockdev: convert drive_mirror to blockdev_mirror
> blockdev: mirror: change aio on target if io_uring is not default.
> blockdev: add backing_chain support
> qcow2: add external snapshot support
>
> PVE/QemuConfig.pm | 4 +-
> PVE/QemuMigrate.pm | 2 +-
> PVE/QemuServer.pm | 946 ++++++++++++++----
> test/cfg2cmd/bootorder-empty.conf.cmd | 12 +-
> test/cfg2cmd/bootorder-legacy.conf.cmd | 12 +-
> test/cfg2cmd/bootorder.conf.cmd | 12 +-
> ...putype-icelake-client-deprecation.conf.cmd | 6 +-
> test/cfg2cmd/ide.conf.cmd | 23 +-
> test/cfg2cmd/pinned-version-pxe-pve.conf.cmd | 6 +-
> test/cfg2cmd/pinned-version-pxe.conf.cmd | 6 +-
> test/cfg2cmd/pinned-version.conf.cmd | 6 +-
> test/cfg2cmd/q35-ide.conf.cmd | 23 +-
> .../q35-linux-hostpci-template.conf.cmd | 3 +-
> test/cfg2cmd/seabios_serial.conf.cmd | 6 +-
> ...imple-balloon-free-page-reporting.conf.cmd | 6 +-
> test/cfg2cmd/simple-btrfs.conf.cmd | 6 +-
> test/cfg2cmd/simple-virtio-blk.conf.cmd | 6 +-
> test/cfg2cmd/simple1-template.conf.cmd | 11 +-
> test/cfg2cmd/simple1.conf.cmd | 6 +-
> 19 files changed, 830 insertions(+), 272 deletions(-)
>
>
> pve-qemu:
>
> add block-commit-replaces option patch
>
> ...052-block-commit-add-replaces-option.patch | 137 ++++++++++++++++++
> debian/patches/series | 1 +
> 2 files changed, 138 insertions(+)
> create mode 100644 debian/patches/pve/0052-block-commit-add-replaces-option.patch
>
> --
>
> 2.39.5
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-01-09 14:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 9:12 Alexandre Derumier via pve-devel
2025-01-09 14:13 ` Fabian Grünbichler [this message]
2025-01-10 7:44 ` DERUMIER, Alexandre via pve-devel
2025-01-10 9:55 ` Fiona Ebner
2025-01-10 12:30 ` DERUMIER, Alexandre via pve-devel
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=1841615375.1037.1736431994704@webmail.proxmox.com \
--to=f.gruenbichler@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