From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?iso-8859-1?Q?Marcos_Sim=F3_Pic=F3?= Subject: vTPM issues Date: Wed, 24 Jun 2015 15:16:37 +0000 Message-ID: <1435158998075.14889@kth.se> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6754268677663475490==" Return-path: Content-Language: es-ES 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 --===============6754268677663475490== Content-Language: es-ES Content-Type: multipart/alternative; boundary="_000_143515899807514889kthse_" --_000_143515899807514889kthse_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello everyone, I would like to try the vTPM feature, but I'm having some issues. Basically= , I followed the steps explained in https://mhsamsal.wordpress.com/2013/12/= 05/configuring-virtual-tpm-vtpm-for-xen-4-3-guest-virtual-machines/ I'm running Ubuntu 14.04 as Dom0 on a Dell optiplex-9020. I compiled Xen 4.= 5.0 from source. After creating vtpmmgr and vtpm stubdoms, and DomU, I can = invoke tpm_version from DomU: root@DomU:/home/xen# tpm_version TPM 1.2 Version Info: Chip Version: 1.2.0.7 Spec Level: 2 Errata Revision: 1 TPM Vendor ID: ETHZ TPM Version: 01010000 Manufacturer Info: 4554485a I can also see the PCRs status by invoking cat /sys/class/misc/tpm0/device/= pcrs, however, most of the commands return an error. When I invoke takeowne= rship I get the following error: root@DomU:/home/xen# tpm_takeownership -y -z -l debug Tspi_Context_Create success Tspi_Context_Connect success Tspi_Context_GetTpmObject success Tspi_GetPolicyObject success Tspi_Policy_SetSecret success Tspi_Context_CreateObject success Tspi_GetPolicyObject success Tspi_Policy_SetSecret success Tspi_TPM_TakeOwnership failed: 0x00002004 - layer=3Dtcs, code=3D0004 (4), I= nternal software error Tspi_Context_CloseObject success Tspi_Context_FreeMemory success Tspi_Context_Close success The same error is given when invoking tpm_getpubkey. I have already tried a= fter clearing the TPM from BIOS, after having taken ownership and with owne= rship no taken with the same result when using the vTPM. I have also instal= led Xen 4.3.4, with the same result too. In the end, I would like to use the vTPM to generate and use RSA keys for T= LS session establishing (using the API provided with GnuTLS). Since I canno= t take ownership of the vTPM, the GnuTLS' tpmtool complains it doesn't find= any SRK. I really appreciate any help you can provide. Best regards, Marcos --_000_143515899807514889kthse_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hello everyone,


I would like to try the vTPM feature, but I'm having some issues. Basica= lly, I followed the steps explained in https://mhsamsal.wordpress.com/2013/12/05/configuring-virtual-tpm-vtpm-for-= xen-4-3-guest-virtual-machines/


I'm running Ubuntu 14.04 as Dom0 on a Dell optiplex-9020. I compiled Xen= 4.5.0 from source. After creating vtpmmgr and vtpm stubdoms, and DomU, I c= an invoke tpm_version from DomU:


root@DomU:/home/xen# tpm_version
  TPM 1.2 Version Info:
  Chip Version:        1.2.0.7
  Spec Level:          2<= br>   Errata Revision:     1
  TPM Vendor ID:       ETHZ
  TPM Version:         0101000= 0
  Manufacturer Info:   4554485a


I can also see the PCRs status by invoking cat /sys/class/misc/tpm0/devi= ce/pcrs, however, most of the commands return an error. When I invoke takeo= wnership I get the following error:


root@DomU:/home/xen# tpm_takeownership -y -z -l debug
Tspi_Context_Create success
Tspi_Context_Connect success
Tspi_Context_GetTpmObject success
Tspi_GetPolicyObject success
Tspi_Policy_SetSecret success
Tspi_Context_CreateObject success
Tspi_GetPolicyObject success
Tspi_Policy_SetSecret success
Tspi_TPM_TakeOwnership failed: 0x00002004 - layer=3Dtcs, code=3D0004 (4), I= nternal software error
Tspi_Context_CloseObject success
Tspi_Context_FreeMemory success
Tspi_Context_Close success


The same error is given when invoking tpm_getpubkey. I have already trie= d after clearing the TPM from BIOS, after having taken ownership and with o= wnership no taken with the same result when using the vTPM. I have also ins= talled Xen 4.3.4, with the same result too.


In the end, I would like to use the vTPM to generate and use RSA keys fo= r TLS session establishing (using the API provided with GnuTLS). Since = ;I cannot take ownership of the vTPM, the GnuTLS' tpmtool complains it does= n't find any SRK.


I really appreciate any help you can provide.


Best regards,

Marcos

--_000_143515899807514889kthse_-- --===============6754268677663475490== 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 --===============6754268677663475490==--