From: Thomas Lamprecht <t.lamprecht@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] migrate: skip tpmstate for NBD migration
Date: Tue, 16 Nov 2021 12:12:46 +0100 [thread overview]
Message-ID: <c37e599d-cad4-74f3-fe9b-46d97a958d7d@proxmox.com> (raw)
In-Reply-To: <20211116105215.1812508-1-f.gruenbichler@proxmox.com>
On 16.11.21 11:52, Fabian Grünbichler wrote:
> the tpmstate volume is not available in the VM directly, but we do
> migrate the state volume via a storage migration anyway if necessary.
>
some context would be great to have in the commit message, iow. mentioning
that QEMU is already migrating this as part of its memory/state migration.
Also, how is "migrate -> stop -> start" affected, is the TPM synced out to
the (previously replicated?) disk on the target side during stop?
> this code path was only triggered for replicated VMs with TPM.
>
> Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
> ---
> PVE/QemuServer.pm | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm
> index 580af9e..76d45a2 100644
> --- a/PVE/QemuServer.pm
> +++ b/PVE/QemuServer.pm
> @@ -5238,6 +5238,7 @@ sub vm_migrate_get_nbd_disks {
> my ($ds, $drive) = @_;
>
> return if drive_is_cdrom($drive);
> + return if $ds eq 'tpmstate0';
>
> my $volid = $drive->{file};
>
>
next prev parent reply other threads:[~2021-11-16 11:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 10:52 Fabian Grünbichler
2021-11-16 11:12 ` Thomas Lamprecht [this message]
2021-11-16 11:39 ` Fabian Grünbichler
2021-11-16 11:50 ` Thomas Lamprecht
2021-11-16 13:25 ` [pve-devel] applied: " Thomas Lamprecht
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=c37e599d-cad4-74f3-fe9b-46d97a958d7d@proxmox.com \
--to=t.lamprecht@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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal