From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Fioravante Subject: Re: vTPM setup problem on the emulator Date: Wed, 09 Jan 2013 14:33:00 -0500 Message-ID: <50EDC5EC.7050306@jhuapl.edu> References: <36a97c6a.ff69.13c1e887f12.Coremail.gbtux@126.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7414781137029978556==" Return-path: In-Reply-To: <36a97c6a.ff69.13c1e887f12.Coremail.gbtux@126.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org This is a cryptographically signed message in MIME format. --===============7414781137029978556== Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms050606090101000108080506" This is a cryptographically signed message in MIME format. --------------ms050606090101000108080506 Content-Type: multipart/alternative; boundary="------------030509070207030202000405" This is a multi-part message in MIME format. --------------030509070207030202000405 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable On 01/09/2013 03:58 AM, gavin wrote: > Hi, > > I tried to install the vTPM in Xen-4.1.0 + Dom0 kernel 2.6.18.8 + DomU = > kernel 2.6.18.8. The device is TPM emulator. > However, I encountered several problems. > > 1. In DomU, I run "modprobe tpm_xenu" successfully. But it doesn't=20 > creates the /dev/tpm0 device as our had expected. So, the trousers=20 > cannot be started. An old thread in Xen mail-list can do=20 > this,(http://old-list-archives.xen.org/xense-devel/2006-12/msg00002.htm= l)=20 > but it helps little to me. > Is there any problem with my vTPM front driver? The tpm related=20 > modules and other info in DomU is list here. > *[root@gavin-pv ~]# lsmod | grep tpm* > tpm_xenu 15752 0 [permanent] > tpm 17952 1 tpm_xenu > tpm_bios 10112 1 tpm > *[root@gavin-pv ~]# tcsd -f* > TCSD TDDL ERROR: Could not find a device to open! Any relevant output in dmesg? Also does your domu config file have a=20 vtpm device specified? > 2. In Dom0, I run "modprobe tpmd_dev" and "modprobe tpmbk" also=20 > successfully and I can get the devices /dev/tpm, /dev/tpm0, and=20 > /dev/vtpm. However, I cannot start the tpm emulator (# ./tpmd -f clear = > pvm 1) and vtpm manager (# vtpm_managerd). The related info and output = > error from Dom0 is also list here. So you want to use the TPM emulator on dom0 instead of a physical TPM? I see you listed /dev/tpm and /dev/tpm0. I believe the old manager is=20 hard coded to use the second one. Is tpmd creating both? > *[root@localhost tpmd]# lsmod | grep tpm* > tpmd_dev 10416 0 > tpmbk 19516 0 [permanent] > *[root@localhost tpmd]# ./tpmd -f clear pvm 1* > VTPMD[0]: tpmd.c:766: Info: starting TPM Emulator daemon > VTPMD[0]: tpmd.c:369: Info: parsing options > VTPMD[1]: tpmd.c:478: Info: openening random device /dev/urandom > VTPMD[1]: tpmd.c:621: Info: staring main loop > Loading NVM. > Error in read_from_file:301 > VTPMD[1]: ../tpm/tpm_data.c:83: Info: initializing TPM data to default = > values > VTPMD[1]: ../tpm/tpm_startup.c:30: Info: TPM_Init() > VTPMD[1]: ../tpm/tpm_testing.c:242: Info: TPM_SelfTestFull() > VTPMD[1]: ../tpm/tpm_testing.c:260: Info: Self-Test succeeded > VTPMD[1]: ../tpm/tpm_startup.c:44: Info: TPM_Startup(1) > VTPMD[1]: tpmd.c:661: Error: Failed to open devices to listen to guest.= > > *[root@localhost vtpm]# vtpm_managerd* > INFO[VTPM]: Starting VTPM. > INFO[TCS]: Constructing new TCS: > ERROR[TXDATA]: TPM open failedERROR in VTPM_Init_Manager at=20 > vtpm_manager.c:205 code: > TPM_IOERROR. > ERROR[VTPM]: Closing vtpmd due to error during startup. > > > Thanks in advance for your any reply. > > -- > Best Regards, > Gavin > > --------------030509070207030202000405 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On 01/09/2013 03:58 AM, gavin wrote:
Hi,

I tried to install the vTPM in Xen-4.1.0 + Dom0 kernel 2.6.18.8 + DomU kernel 2.6.18.8. The device is TPM emulator. However, I=C2=A0 encountered several problems.

1. In DomU, I run "modprobe tpm_xenu" successfully. But it doesn't creates the /dev/tpm0 device as our had expected. So, the trousers cannot be started. An old thread in Xen mail-list can do this,(http://old-list-arc= hives.xen.org/xense-devel/2006-12/msg00002.html) but it helps little to me.
Is there any problem with my vTPM front driver? The tpm related modules and other info in DomU is list here. 
[root@gavin-pv ~]# lsmod | grep tpm
tpm_xenu               15752  0 [permanent]
tpm                        17952  1 tpm_xenu
tpm_bios               10112  1 tpm
[root@gavin-pv ~]# tcsd -f
TCSD TDDL ERROR: Could not find a device to open!
Any relevant output in dmesg? Also does your domu config file have a vtpm device specified?

          2. In Dom0, I run "modprobe tpmd_dev" and "modprobe tpmbk"
          also successfully and I can get the devices /dev/tpm,
          /dev/tpm0, and /dev/vtpm. However, I cannot start the tpm
          emulator (# ./tpmd -f clear pvm 1) and vtpm manager (#
          vtpm_managerd). The related info and output error from Dom0 is
          also list here. 

        

      

    

    So you want to use the TPM emulator on dom0 instead of a physical
    TPM? 

    

    I see you listed /dev/tpm and /dev/tpm0. I believe the old manager
    is hard coded to use the second one. Is tpmd creating both? 

    

    

    

      

        

          
[root@localhost tpmd]# lsmod | grep tpm
tpmd_dev               10416  0=20
tpmbk                     19516  0 [permanent]

          [root@localhost tpmd]# ./tpmd -f clear pvm 1

          VTPMD[0]: tpmd.c:766: Info: starting TPM Emulator daemon

          VTPMD[0]: tpmd.c:369: Info: parsing options

          VTPMD[1]: tpmd.c:478: Info: openening random device
          /dev/urandom

          VTPMD[1]: tpmd.c:621: Info: staring main loop

          Loading NVM.

          Error in read_from_file:301

          VTPMD[1]: ../tpm/tpm_data.c:83: Info: initializing TPM data to
          default values

          VTPMD[1]: ../tpm/tpm_startup.c:30: Info: TPM_Init()

          VTPMD[1]: ../tpm/tpm_testing.c:242: Info: TPM_SelfTestFull()
          VTPMD[1]: ../tpm/tpm_testing.c:260: Info: Self-Test succeeded
          VTPMD[1]: ../tpm/tpm_startup.c:44: Info: TPM_Startup(1)

          VTPMD[1]: tpmd.c:661: Error: Failed to open devices to listen
          to guest.

        

      

    

    

    

    

      

        


          [root@localhost vtpm]# vtpm_managerd

          INFO[VTPM]: Starting VTPM.

          INFO[TCS]: Constructing new TCS:

          ERROR[TXDATA]: TPM open failedERROR in VTPM_Init_Manager at
          vtpm_manager.c:205 code:

          TPM_IOERROR.

          ERROR[VTPM]: Closing vtpmd due to error during startup.

          

          

          Thanks in advance for your any reply.

          

          
--

            Best Regards,
            
Gavin

          

        

      

      

      

      
    

    

  


--------------030509070207030202000405--

--------------ms050606090101000108080506
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIDyjCC
A8YwggMvoAMCAQICBD/xyf0wDQYJKoZIhvcNAQEFBQAwLzELMAkGA1UEBhMCVVMxDzANBgNV
BAoTBkpIVUFQTDEPMA0GA1UECxMGQklTRENBMB4XDTEwMDYxMTE4MjIwNloXDTEzMDYxMTE4
NTIwNlowZjELMAkGA1UEBhMCVVMxDzANBgNVBAoTBkpIVUFQTDEPMA0GA1UECxMGUGVvcGxl
MTUwFgYDVQQLEw9WUE5Hcm91cC1CSVNEQ0EwGwYDVQQDExRNYXR0aGV3IEUgRmlvcmF2YW50
ZTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAnpbwVSP6o1Nb5lcW7dd3yTo9iBJdi7qz
4nANOMFPK7JOy5npKN1iiousl28U/scUJES55gPwAWYJK3uVyQAsA4adgDKi5DoD1UHDQEwp
bY7iHLJeq0NPr4BqYNqnCFPbE6HC8zSJrr4qKn+gVUQT39SIFqdiIPJwZL8FYTRQ/zsCAwEA
AaOCAbYwggGyMAsGA1UdDwQEAwIHgDArBgNVHRAEJDAigA8yMDEwMDYxMTE4MjIwNlqBDzIw
MTIwNzE3MjI1MjA2WjAbBg0rBgEEAbMlCwMBAQEBBAoWCGZpb3JhbWUxMBsGDSsGAQQBsyUL
AwEBAQIEChIIMDAxMDQyNjEwWAYJYIZIAYb6ax4BBEsMSVRoZSBwcml2YXRlIGtleSBjb3Jy
ZXNwb25kaW5nIHRvIHRoaXMgY2VydGlmaWNhdGUgbWF5IGhhdmUgYmVlbiBleHBvcnRlZC4w
KAYDVR0RBCEwH4EdTWF0dGhldy5GaW9yYXZhbnRlQGpodWFwbC5lZHUwUgYDVR0fBEswSTBH
oEWgQ6RBMD8xCzAJBgNVBAYTAlVTMQ8wDQYDVQQKEwZKSFVBUEwxDzANBgNVBAsTBkJJU0RD
QTEOMAwGA1UEAxMFQ1JMNTYwHwYDVR0jBBgwFoAUCDUpmxH52EU2CyWmF2EJMB1yqeswHQYD
VR0OBBYEFO6LYxg6r9wHZ+zdQtBHn1dZ/YTNMAkGA1UdEwQCMAAwGQYJKoZIhvZ9B0EABAww
ChsEVjcuMQMCBLAwDQYJKoZIhvcNAQEFBQADgYEAJO9HQh4YNChVLzuZqK5ARJARD8JoujGZ
fdo75quvg2jXFQe2sEjvLnxJZgm/pv8fdZakq48CWwjYHKuvIp7sDjTEsQfo+y7SpN/N2NvJ
WU5SqfK1VgYtNLRRoGJUB5Q1aZ+Dg95g3kqpyfpUMISJL8IKVLtJVfN4fggFVUYZ9wwxggGr
MIIBpwIBATA3MC8xCzAJBgNVBAYTAlVTMQ8wDQYDVQQKEwZKSFVBUEwxDzANBgNVBAsTBkJJ
U0RDQQIEP/HJ/TAJBgUrDgMCGgUAoIHLMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJ
KoZIhvcNAQkFMQ8XDTEzMDEwOTE5MzMwMFowIwYJKoZIhvcNAQkEMRYEFINrRhMrtamMSrj9
/w+BoLb30bztMGwGCSqGSIb3DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAK
BggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYI
KoZIhvcNAwICASgwDQYJKoZIhvcNAQEBBQAEgYCTq1ROIfNRNj8qy5ofCHe+V4n2esUudmmA
P+BS4p4Bkox/huLjCR0C6X8P+6wz/xogYdn0PoUXFOgBc+mJEQy8IHRQYpIL/aEiihLBy8B4
+Bb8ypG+Tl45LBxq30LCM7lCr5eV+ZEFIrj1todb9p/5LoY/o8PBKMppwEpV4qZmAgAAAAAA
AA==
--------------ms050606090101000108080506--


--===============7414781137029978556==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============7414781137029978556==--