From: Stefan Berger <stefanb@linux.ibm.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
qemu-devel@nongnu.org
Cc: "Daniel P . Berrangé" <berrange@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>
Subject: Re: [PATCH v10 2/2] tpm: add backend for mssim
Date: Wed, 1 May 2024 12:31:14 -0400 [thread overview]
Message-ID: <8347cf6a-7c9f-48f8-a3a7-4053aefd2176@linux.ibm.com> (raw)
In-Reply-To: <c97f84c7d6e026450644466313b6347b00841a43.camel@HansenPartnership.com>
On 5/1/24 12:21, James Bottomley wrote:
> On Tue, 2024-04-30 at 17:12 -0400, Stefan Berger wrote:
>> On 4/30/24 15:08, James Bottomley wrote:
> [...]
>>> +The mssim backend supports snapshotting and migration by not
>>> resetting
>>
>> I don't thing snapshotting is supported because snapshooting would
>> require you to be able to set the state of the vTPM from the snapshot
>> you started. I would remove the claim.
>
> I thought we established last time that it can definitely do both (and
> I've tested it because you asked me to). Snapshotting and migration
> are essentially the same thing, with snapshotting being easier because
> it can be done on the same host meaning the same command line
> parameters. If you migrate to a different host you need the socket to
> point back to the host serving the vTPM.
>
> To do this easily you simply keep the vTPM running while the VM is
> undergoing snapshot and migration. If you're thinking of and extended
> down time for the snapshot, then it's up to the vTPM implementation to
> store the state (or simply keep it running for an extended time doing
> nothing).
Which part of the code injects the state into the vTPM so that it
resumes with the state of the TPM (PCRs, NVRAM indices, keys, sessions
etc.) from when the snapshot was taken?
>
>
>> Rest LGTM.
>
> Thanks!
>
> Regards,
>
> James
>
next prev parent reply other threads:[~2024-05-01 16:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 19:08 [PATCH v10 0/2] tpm: add mssim backend James Bottomley
2024-04-30 19:08 ` [PATCH v10 1/2] tpm: convert tpmdev options processing to new visitor format James Bottomley
2024-05-02 8:35 ` Markus Armbruster
2024-04-30 19:08 ` [PATCH v10 2/2] tpm: add backend for mssim James Bottomley
2024-04-30 21:12 ` Stefan Berger
2024-05-01 16:21 ` James Bottomley
2024-05-01 16:31 ` Stefan Berger [this message]
2024-05-01 16:52 ` James Bottomley
2024-05-01 17:20 ` Stefan Berger
2024-05-01 18:22 ` James Bottomley
2024-04-30 21:02 ` [PATCH v10 0/2] tpm: add mssim backend Stefan Berger
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=8347cf6a-7c9f-48f8-a3a7-4053aefd2176@linux.ibm.com \
--to=stefanb@linux.ibm.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).