From: Fiona Ebner <f.ebner@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>,
"Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Subject: Re: [pve-devel] [PATCH qemu-server] snapshot: prohibit live snapshot (remove) of qcow2 TPM drive on storage with snapshot-as-volume-chain
Date: Wed, 19 Nov 2025 13:34:36 +0100 [thread overview]
Message-ID: <ccbebc31-38db-47ed-aa8f-3c8dbeaefe3a@proxmox.com> (raw)
In-Reply-To: <1763554018.7340b0hkru.astroid@yuna.none>
Am 19.11.25 um 1:06 PM schrieb Fabian Grünbichler:
> On November 19, 2025 12:59 pm, Fiona Ebner wrote:
>> QSD and swtpm currently are not prepared for dealing with
>> blockdev-replace and rename operations that snapshot or snapshot
>> remove operations with a snapshot-as-volume-chain storage entail.
>>
>> Reported-by: Friedrich Weber <f.weber@proxmox.com>
>> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
>
> Reviewed-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
>
> unfortunate, but we have to live with this limitation for now..
I'll look into sending the 'blockdev-replace', etc. QMP commands to QSD
instead of QEMU for TPM. We'll see if it says something like "can't
replace, because active export", but might just require some additional
implementation in QSD then. I don't see a fundamental limitation (yet).
_______________________________________________
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-11-19 12:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 11:59 Fiona Ebner
2025-11-19 12:07 ` Fabian Grünbichler
2025-11-19 12:34 ` Fiona Ebner [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=ccbebc31-38db-47ed-aa8f-3c8dbeaefe3a@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.