From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: pve-devel@lists.proxmox.com, Fiona Ebner <f.ebner@proxmox.com>
Subject: Re: [PATCH-SERIES qemu-server 0/2] partially fix #7554: avoid incorrectly offline migrating qcow2 on LVM as raw
Date: Tue, 16 Jun 2026 14:35:50 +0200 [thread overview]
Message-ID: <178161334539.1984719.16245702707423859259.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260601145528.285536-1-f.ebner@proxmox.com>
On Mon, 01 Jun 2026 16:55:00 +0200, Fiona Ebner wrote:
> Because volumes were not activated early for offline migration,
> getting the size and as a consequence the format would not work for
> qcow2 on LVM. But migration also continued and not having the format
> would lead to the 'with-snapshots' parameter not being set, despite
> the format being qcow2 and so the migration would wrongly continue
> with raw+size as the stream format. If 'with-snapshots' were set, the
> plugin would correctly report that there is no possible transfer
> format (the same restriction is present in file-based storages with
> snapshot-as-volume-chain).
>
> [...]
Applied, thanks!
[1/2] migration: local volume: abort early when size or format cannot be determined
commit: fafc9e4002ecbb0b7afa6380f7070c438c708370
[2/2] migration: local volume: activate for querying the size (required for qcow2 on LVM)
commit: a82047357aa92f5bad6b3847e5047defa65d1a0e
Best regards,
--
Fabian Grünbichler <f.gruenbichler@proxmox.com>
prev parent reply other threads:[~2026-06-16 12:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 14:55 [PATCH-SERIES qemu-server 0/2] partially fix #7554: avoid incorrectly offline migrating qcow2 on LVM as raw Fiona Ebner
2026-06-01 14:55 ` [PATCH qemu-server 1/2] migration: local volume: abort early when size or format cannot be determined Fiona Ebner
2026-06-01 14:55 ` [PATCH qemu-server 2/2] migration: local volume: activate for querying the size (required for qcow2 on LVM) Fiona Ebner
2026-06-16 12:35 ` Fabian Grünbichler [this message]
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=178161334539.1984719.16245702707423859259.b4-ty@proxmox.com \
--to=f.gruenbichler@proxmox.com \
--cc=f.ebner@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