xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Fioravante <matthew.fioravante@jhuapl.edu>
To: Jordi Cucurull Juan <jordi.cucurull@scytl.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Compile Xen with VTPM support
Date: Fri, 28 Sep 2012 09:55:36 -0400	[thread overview]
Message-ID: <5065AC58.4010309@jhuapl.edu> (raw)
In-Reply-To: <506553C5.3090507@scytl.com>


[-- Attachment #1.1: Type: text/plain, Size: 1856 bytes --]

It uses the physical tpm. Hopefully they should all be in within a
month. Were working on it now.

On 09/28/2012 03:37 AM, Jordi Cucurull Juan wrote:
> Hi Matthew,
>
> As a rough approximation, when are you planning to submit the new vtpm 
> implementation? In the new coming weeks, months, year?
>
> And, is this new vtpm going to be linked to the physical tpm of the 
> machine or is going to be totally independent of it?
>
> Best,
> Jordi
>
>
> On 09/27/2012 05:43 PM, Matthew Fioravante wrote:
>> The current (old) vtpm implementation still sort of works. You have to
>> use xm and find a linux kernel with the tpmfront and tpmback drivers. I
>> believe the original xen 2.6.18 kernel has them. There may or may not be
>> newer kernels with these drivers.
>>
>> docs/misc/vtpm.txt should have everything you need to use it.
>>
>> That being said I'm in the process of submitting my new vtpm
>> implementation. So keep an eye on that activity if you're interested.
>>
>> On 09/27/2012 11:40 AM, Jordi Cucurull Juan wrote:
>>> Dear all,
>>>
>>> I am trying to compile Xen 4.2.0 with VTPM support. The documentation
>>> available inside Xen is from 2006. I am wondering if the current steps
>>> to enable VTPM support are the same written in the documentation or they
>>> have changed.
>>>
>>> Is it enough with setting the "--enable-vtpm" argument during the
>>> configure process? Furthermore, at that time Xen was providing the Linux
>>> Kernel as part of its sources. Have the current kernels to be patched to
>>> include the Xen VTPM drivers? If it is the case, where can we find the
>>> patches?
>>>
>>> Thank you in advance!
>>> Jordi.
>>>
>>>
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xen.org
>>> http://lists.xen.org/xen-devel
>



[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 1459 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

      reply	other threads:[~2012-09-28 13:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-27 15:40 Compile Xen with VTPM support Jordi Cucurull Juan
2012-09-27 15:43 ` Matthew Fioravante
2012-09-28  7:37   ` Jordi Cucurull Juan
2012-09-28 13:55     ` Matthew Fioravante [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=5065AC58.4010309@jhuapl.edu \
    --to=matthew.fioravante@jhuapl.edu \
    --cc=jordi.cucurull@scytl.com \
    --cc=xen-devel@lists.xen.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).