public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: Thomas Ellmenreich <t.ellmenreich@proxmox.com>,
	pve-devel@lists.proxmox.com
Subject: Re: [PATCH qemu-server 2/5] drive: update TPM size on creation
Date: Tue, 20 Oct 2026 14:28:57 +0200	[thread overview]
Message-ID: <77119e52-f895-4a0b-b48a-42b0745276f8@proxmox.com> (raw)
In-Reply-To: <20261019095346.175659-3-t.ellmenreich@proxmox.com>

The commit subject should start out with "api: create disks:"

Am 19.10.26 um 11:53 AM schrieb Thomas Ellmenreich:
> When creating a TPM drive, the default size is 4MiB. This default is
> constant and cannot be changed, unless the backing storage has a bigger
> granularity, in which case it is forcibly changed to the bigger size.
> 
> To directly show the correct size of a TPM drive, query its size after
> creation, and set that as the drive size.
> 
> Suggested-by: Fiona Ebner <f.ebner@proxmox.com>
> Signed-off-by: Thomas Ellmenreich <t.ellmenreich@proxmox.com>

With the commit subject and nits addressed:
Reviewed-by: Fiona Ebner <f.ebner@proxmox.com>

> ---
>  src/PVE/API2/Qemu.pm | 16 ++++++++++++----
>  1 file changed, 12 insertions(+), 4 deletions(-)
> 
> diff --git a/src/PVE/API2/Qemu.pm b/src/PVE/API2/Qemu.pm
> index cfbc1f51..e42cad74 100644
> --- a/src/PVE/API2/Qemu.pm
> +++ b/src/PVE/API2/Qemu.pm
> @@ -665,13 +665,21 @@ my sub create_disks : prototype($$$$$$$$$$$) {
>                          $storecfg, $storeid, $vmid, $fmt, $arch, $disk, $smm, $cvm_type,
>                      );
>                  } elsif ($ds eq 'tpmstate0') {
> -                    # A fixed size is used for TPM state volumes
> -                    $size = PVE::Tools::convert_size(
> +

Style nit: blank line here is inconsistent with the surrounding style

> +                    # A fixed size is requested for TPM state volumes, but the
> +                    # storage might increase it up to its allocation granularity
> +                    my $target_size = PVE::Tools::convert_size(
>                          PVE::QemuServer::Drive::TPMSTATE_DISK_SIZE,
>                          'b' => 'kb',
>                      );
> -                    $volid =
> -                        PVE::Storage::vdisk_alloc($storecfg, $storeid, $vmid, $fmt, undef, $size);
> +

Style nit: I'd drop this blank too, since otherwise the first bit with
the comment feels a bit detached

> +                    $volid = PVE::Storage::vdisk_alloc(
> +                        $storecfg, $storeid, $vmid, $fmt, undef, $target_size,
> +                    );
> +                    $size = PVE::Tools::convert_size(
> +                        PVE::QemuServer::get_tpmstate_size($volid, $storecfg),
> +                        'b' => 'kb',
> +                    );
>                  } else {
>                      $volid =
>                          PVE::Storage::vdisk_alloc($storecfg, $storeid, $vmid, $fmt, undef, $size);





  reply	other threads:[~2026-10-20 12:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-19  9:53 [RFC qemu-server 0/5] drive: account for differing TPM sizes Thomas Ellmenreich
2026-10-19  9:53 ` [PATCH qemu-server 1/5] drive: improve and extend TPM drive size helpers Thomas Ellmenreich
2026-10-20 12:28   ` Fiona Ebner
2026-10-19  9:53 ` [PATCH qemu-server 2/5] drive: update TPM size on creation Thomas Ellmenreich
2026-10-20 12:28   ` Fiona Ebner [this message]
2026-10-19  9:53 ` [PATCH qemu-server 3/5] drive: read actual size when cloning TPM drive Thomas Ellmenreich
2026-10-20 12:28   ` Fiona Ebner
2026-10-19  9:53 ` [PATCH qemu-server 4/5] tests: make qm mock accept disk command Thomas Ellmenreich
2026-10-20 12:28   ` Fiona Ebner
2026-10-19  9:53 ` [PATCH qemu-server 5/5] drive: rescan drives after migrating to different storage Thomas Ellmenreich
2026-10-20 12:28   ` Fiona Ebner
2026-10-20 12:28 ` [RFC qemu-server 0/5] drive: account for differing TPM sizes Fiona Ebner

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=77119e52-f895-4a0b-b48a-42b0745276f8@proxmox.com \
    --to=f.ebner@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=t.ellmenreich@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal