From: Kent Yoder <key@linux.vnet.ibm.com>
To: Jordi Cucurull Juan <jordi.cucurull@scytl.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] TPM does not seem to work under QEMU with TPM patches
Date: Mon, 20 Aug 2012 15:14:54 -0500 [thread overview]
Message-ID: <20120820201451.GA19204@linux.vnet.ibm.com> (raw)
In-Reply-To: <5032B65C.3000009@scytl.com>
Hi Jordi,
On Mon, Aug 20, 2012 at 06:12:44PM -0400, Jordi Cucurull Juan wrote:
> Dear all,
>
> I am testing the TPM patches of Stefan Berger to provide TPM support
> to QEMU. Nevertheless I have not managed to run them successfully.
> During the compilation of QEMU with his patches (V18 for revision
> 563987d) I have not had any issue. But, I have a virtual machine
> based on CentOS 6.2 and the TPM does not seem to be present. I run
> the machine with the following command line (as a root user):
>
> # /usr/local/bin/qemu-system-x86_64 -hda qemu-disk-centos.img -m
> 1024 -boot d -enable-kvm -usbdevice tablet -k es -tpmdev
> passthrough,id=tpm0,path=/dev/tpm0 -device tpm-tis,tpmdev=tpm0
>
> My real machine has an Infineon TPM v1.2. When I try to load the TSS
> library (Trousers) inside the client machine (the CentOS 6.2) it
> throws the following error:
>
> insmod: error inserting '/lib/modules/2.6.32-279.5.1.el6.x86_64/kernel/drivers/char/tpm/tpm_atmel.ko':
> -1 no such device
This should be fine - the tpm_tis driver should be driving the vtpm.
>
> Apart from this, QEMU does not throw any error. Should I enable
> something else to have access to the TPM? In addition, I do not see
> any /dev/vtpm0 device in my real machine.
As I understand them, the qemu patches allow direct writing from the
guest to the host's /dev/tpm0, so you wouldn't see a new device node.
Kent
>
> Best regards,
> Jordi.
>
>
> --
> Jordi Cucurull Juan
> Researcher
> Scytl Secure Electronic Voting
> Plaça Gal·la Placidia, 1-3, 1st floor · 08006 Barcelona
> Phone: + 34 934 230 324
> Fax + 34 933 251 028
> jordi.cucurull@scytl.com
> http://www.scytl.com
>
> NOTICE: The information in this e-mail and in any of its attachments is confidential and intended solely for the attention and use of the named addressee(s). If you are not the intended recipient, any disclosure, copying, distribution or retaining of this message or any part of it, without the prior written consent of Scytl Secure Electronic Voting, SA is prohibited and may be unlawful. If you have received this in error, please contact the sender and delete the material from any computer.
>
> Your data are in a file owned by Scytl Secure Electronic Voting, S.A. You can exercice your rights of access, rectification, cancellation and opposition by contacting Scytl Secure Electronic Voting, S.A. at the following address: Gal·la Placídia, 1-3. 1st, 08006 Barcelona (Spain), according to the Organic Law 15/1999, of 13th December of Protection of Personal Data.
>
>
next prev parent reply other threads:[~2012-08-20 20:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 22:12 [Qemu-devel] TPM does not seem to work under QEMU with TPM patches Jordi Cucurull Juan
2012-08-20 20:14 ` Kent Yoder [this message]
2012-08-21 10:24 ` Jordi Cucurull Juan
2012-08-29 13:07 ` 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=20120820201451.GA19204@linux.vnet.ibm.com \
--to=key@linux.vnet.ibm.com \
--cc=jordi.cucurull@scytl.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).