From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Fiona Ebner <f.ebner@proxmox.com>
Subject: [pve-devel] applied: [PATCH-SERIES qemu-server 0/3] image convert: fix handling qcow2 on snapshot-as-volume-chain dir target
Date: Thu, 31 Jul 2025 00:23:31 +0200 [thread overview]
Message-ID: <175391420868.4125859.17199922121982504858.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250730150325.138087-1-f.ebner@proxmox.com>
On Wed, 30 Jul 2025 17:03:14 +0200, Fiona Ebner wrote:
> As reported by Friedrich, having qcow2 on a snapshot-as-volume-chain
> directory storage be the target would fail with:
> > Block format 'qcow2' does not support the option 'zeroinit:driver'
>
> First patch is to work around this by just not specifying zeroinit
> which leads to a performance penalty.
>
> [...]
Applied, thanks!
[1/3] image convert: avoid combining target image options and zeroinit filter
commit: 4866264c595c119dbad4ab742cbbd3f6f67f2253
[2/3] image convert: re-use generate_drive_blockdev()
commit: 659b0716cee24e6374b7a35c7204ddc1a3d8a7fc
[3/3] image convert: make using zeroinit with target-image-opts work
commit: f27115cede9b16f83213dafe49a32cc8f2facc2c
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-07-30 22:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 15:03 [pve-devel] " Fiona Ebner
2025-07-30 15:03 ` [pve-devel] [PATCH qemu-server 1/3] image convert: avoid combining target image options and zeroinit filter Fiona Ebner
2025-07-30 15:03 ` [pve-devel] [PATCH qemu-server 2/3] image convert: re-use generate_drive_blockdev() Fiona Ebner
2025-07-30 15:03 ` [pve-devel] [PATCH qemu-server 3/3] image convert: make using zeroinit with target-image-opts work Fiona Ebner
2025-07-30 22:23 ` Thomas Lamprecht [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=175391420868.4125859.17199922121982504858.b4-ty@proxmox.com \
--to=t.lamprecht@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