From: Daniel De Graaf <dgdegra@tycho.nsa.gov>
To: Aastha Mehta <aasthakm@gmail.com>
Cc: George Dunlap <dunlapg@umich.edu>, xen-devel <Xen-devel@lists.xen.org>
Subject: Re: regarding vtpm setup
Date: Fri, 07 Mar 2014 10:57:26 -0500 [thread overview]
Message-ID: <5319EC66.5080200@tycho.nsa.gov> (raw)
In-Reply-To: <CAEx9m44u=KZmbNTF84R0sOgwusdpCeaW7y7n_zvecW_KHmG0Zw@mail.gmail.com>
On 03/07/2014 07:19 AM, Aastha Mehta wrote:
> Hello,
>
> Thank you for your response.
>
[...]
>>
>>
>> Have you tested to see if the vTPM shows up in the guest? If so, can you use
>> it?
>>
>
> I can see /dev/tpm0 in the guest. And I am able to use the vtpm in the
> guest So far, I did only tpm_version, but I see messages showing up on
> the vtpm and the vtpmmgr console.
This indicates that the vTPM is working as it is supposed to.
>> What do the Xenstore entries for the vtpm devices look like (from
>> xenstore-ls)?
>>
>> Do the event channels there match with the event channel dump (xl debug-key
>> e)?
>>
>
> I see a lot of entries in xl debug-keys dump. I can match all the
> event channels in the xenstore entries with the ones from xl
> debug-keys dump. However, there are some entries in xl debug-keys
> which I cannot find in xenstore. I do not understand what those are..
>
> The ones that match are appended with "<<".
> Note, vtpmmgr = domid 2, vtpm = domid 3, guest = domid 4.
Event channels can be created for other reasons besides those recorded
in xenstore: the xenstore event channel itself and the guest console
are some examples. If you are getting TPM responses, the event channels
are wired up correctly.
--
Daniel De Graaf
National Security Agency
prev parent reply other threads:[~2014-03-07 15:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-01 18:43 regarding vtpm setup Aastha Mehta
2014-03-04 11:32 ` Aastha Mehta
2014-03-04 13:46 ` George Dunlap
2014-03-04 20:39 ` Daniel De Graaf
2014-03-07 12:19 ` Aastha Mehta
2014-03-07 15:57 ` Daniel De Graaf [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=5319EC66.5080200@tycho.nsa.gov \
--to=dgdegra@tycho.nsa.gov \
--cc=Xen-devel@lists.xen.org \
--cc=aasthakm@gmail.com \
--cc=dunlapg@umich.edu \
/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).