From: David Edmondson <dme@dme.org>
To: qemu-devel@nongnu.org
Subject: Re: [PATCH v2] docs/specs/tpm: Clarify command line parameters for network migration
Date: Thu, 14 Oct 2021 12:46:30 +0100 [thread overview]
Message-ID: <cun35p3esmh.fsf@dme.org> (raw)
In-Reply-To: 20211014032700.3864022-1-stefanb@linux.ibm.com
On Wednesday, 2021-10-13 at 23:27:00 -04, Stefan Berger wrote:
> Clarify the command line parameters for swtpm migration across the network
> for the case of shared storage and non-shared storage.
>
> Signed-off-by: Stefan Berger <stefanb@linux.ibm.com>
> ---
> docs/specs/tpm.rst | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/docs/specs/tpm.rst b/docs/specs/tpm.rst
> index 3be190343a..956f2c13dc 100644
> --- a/docs/specs/tpm.rst
> +++ b/docs/specs/tpm.rst
> @@ -482,7 +482,8 @@ VM migration across the network:
> - QEMU command line parameters should be identical apart from the
> '-incoming' option on the destination side
>
> - - swtpm command line parameters should be identical
> + - swtpm command line parameters can be identical if storage is not
> + shared and should be different for shared storage
I would interpret this as relating to the storage of the VM (virtual
disk devices), but you are referring to the storage used by swtpm,
presumably.
How about:
- typically, swtpm command line parameters should be different if the
vTPM state directory is on shared storage, and should be the same if
the vTPM state directory is not shared.
>
> VM Snapshotting:
> - QEMU command line parameters should be identical
prev parent reply other threads:[~2021-10-14 11:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 3:27 [PATCH v2] docs/specs/tpm: Clarify command line parameters for network migration Stefan Berger
2021-10-14 11:46 ` David Edmondson [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=cun35p3esmh.fsf@dme.org \
--to=dme@dme.org \
--cc=qemu-devel@nongnu.org \
/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.