From: Fabian Ebner <f.ebner@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] applied: [PATCH qemu-server] clone disk: force raw format for TPM state
Date: Thu, 17 Feb 2022 14:55:47 +0100 [thread overview]
Message-ID: <ed2e73d7-e07b-ede2-0b84-1839a0d4182f@proxmox.com> (raw)
In-Reply-To: <7cd9f084-8065-4c3f-8a65-a1df2021a848@proxmox.com>
Am 17.02.22 um 14:33 schrieb Thomas Lamprecht:
> On 16.02.22 11:47, Fabian Ebner wrote:
>> The format can't be qcow2 for TPM state, because swtpm reads the file
>> directly expecting raw data.
>>
>> Signed-off-by: Fabian Ebner <f.ebner@proxmox.com>
>> ---
>>
>> The DiskStorageSelector in the UI hides the format for TPM state, but
>> still sends along format=qcow2 triggering this bug. Still, the fix
>> should be in the backend.
>>
>
> IMO the frontend shouldn't send that though and in a next major version the backend
> should bail on that, as it can be confusing to do such things "magically".
>
AFAICT the format parameter for disks is mostly (always?) treated as a
suggestion and quietly ignored if the storage doesn't support it. It
happens for clone (not limited to tpmstate0), allocation via pvesm
alloc, allocation via special <storeid>:0 syntax, importdisk.
Of course fixing the frontend for tpmstate0 still makes sense, but I
wonder if all of the above should be changed then?
>> PVE/QemuServer.pm | 1 +
>> 1 file changed, 1 insertion(+)
>>
>>
>
> applied, thanks!
prev parent reply other threads:[~2022-02-17 13:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 10:47 [pve-devel] " Fabian Ebner
2022-02-17 13:33 ` [pve-devel] applied: " Thomas Lamprecht
2022-02-17 13:55 ` Fabian 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=ed2e73d7-e07b-ede2-0b84-1839a0d4182f@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@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