From: "Serge E. Hallyn" <serge@hallyn.com>
To: Stefan Berger <stefanb@linux.vnet.ibm.com>
Cc: serge@hallyn.com, qemu-devel@nongnu.org, andreas.niederl@iaik.tugraz.at
Subject: Re: [Qemu-devel] [PATCH V4 01/10] Support for TPM command line options
Date: Tue, 17 May 2011 15:58:32 -0500 [thread overview]
Message-ID: <20110517205832.GA21516@mail.hallyn.com> (raw)
In-Reply-To: <20110506173244.297608456@linux.vnet.ibm.com>
Quoting Stefan Berger (stefanb@linux.vnet.ibm.com):
> This patch adds support for TPM command line options.
> The command line supported here (considering the libtpms based
> backend) are
>
> ./qemu-... -tpm type=<type>,path=<path to blockstorage file>,
Hm, I did
kvm -tpm type=builtin,path=tpm.img -m 1G disk.img -vnc :1
with disk.img being a newly installed VM. I installed trousers
and tpm-tools, tried loading the tpm, tpm_tis, tpm_infineon, and
some other modules, /dev/tpm was never created, and
tpm_takeownership
continued to give me:
Tspi_Context_Connect failed: 0x00003011 - layer=tsp, code=0011 (17), Communication failure
Which kernel module should work with builtin?
thanks,
-serge
next prev parent reply other threads:[~2011-05-17 20:58 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 17:32 [Qemu-devel] [PATCH V4 00/10] Qemu Trusted Platform Module (TPM) integration Stefan Berger
2011-05-06 17:32 ` [Qemu-devel] [PATCH V4 01/10] Support for TPM command line options Stefan Berger
2011-05-06 20:23 ` Serge E. Hallyn
2011-05-06 20:32 ` Stefan Berger
2011-05-06 20:33 ` Serge E. Hallyn
2011-05-17 20:58 ` Serge E. Hallyn [this message]
2011-05-17 23:15 ` Stefan Berger
2011-05-18 1:52 ` Serge E. Hallyn
2011-05-17 23:16 ` Stefan Berger
2011-05-06 17:32 ` [Qemu-devel] [PATCH V4 02/10] Add TPM (frontend) hardware interface (TPM TIS) to Qemu Stefan Berger
2011-05-07 1:54 ` Serge E. Hallyn
2011-05-18 7:23 ` Markus Armbruster
2011-05-18 10:53 ` Stefan Berger
2011-05-06 17:32 ` [Qemu-devel] [PATCH V4 03/10] Add persistent state handling to TPM TIS frontend driver Stefan Berger
2011-05-18 7:25 ` Markus Armbruster
2011-05-18 10:51 ` Stefan Berger
2011-05-25 14:49 ` Stefan Berger
2011-05-06 17:32 ` [Qemu-devel] [PATCH V4 04/10] Add tpm_tis driver to build process Stefan Berger
2011-05-06 17:32 ` [Qemu-devel] [PATCH V4 05/10] Add a debug register Stefan Berger
2011-05-06 17:32 ` [Qemu-devel] [PATCH V4 06/10] Add a TPM backend skeleton implementation Stefan Berger
2011-05-06 17:32 ` [Qemu-devel] [PATCH V4 07/10] Implementation of the libtpms-based backend Stefan Berger
2011-05-06 17:32 ` [Qemu-devel] [PATCH V4 08/10] Introduce file lock for the block layer Stefan Berger
2011-05-06 17:32 ` [Qemu-devel] [PATCH V4 09/10] Add block storage support for libtpms based TPM backend Stefan Berger
2011-05-06 17:32 ` [Qemu-devel] [PATCH V4 10/10] Encrypt state blobs using AES CBC encryption Stefan Berger
2011-05-09 14:21 ` [Qemu-devel] [PATCH V4 00/10] Qemu Trusted Platform Module (TPM) integration Serge E. Hallyn
2011-05-09 17:37 ` Stefan Berger
2011-05-10 4:07 ` Serge E. Hallyn
2011-05-10 10:46 ` Stefan Berger
2011-05-10 11:59 ` Serge E. Hallyn
2011-05-10 12:43 ` Stefan Berger
2011-05-10 14:20 ` Serge E. Hallyn
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=20110517205832.GA21516@mail.hallyn.com \
--to=serge@hallyn.com \
--cc=andreas.niederl@iaik.tugraz.at \
--cc=qemu-devel@nongnu.org \
--cc=stefanb@linux.vnet.ibm.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 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).