qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: anshul makkar <anshul.makkar@citrix.com>
To: qemu-devel@nongnu.org
Cc: stefanb@us.ibm.com
Subject: [Qemu-devel] CUSE-TPM : Win 10 reports TPM device doesn't have sufficient resources
Date: Tue, 18 Apr 2017 18:42:08 +0100	[thread overview]
Message-ID: <152817b5-89cf-14fe-d83a-bb5c8d748c90@citrix.com> (raw)

Hi,


I am using CUSE-TPM based on

https://github.com/stefanberger/qemu-tpmbranch: 2.4.1+tpm


https://github.com/stefanberger/swtpm


https://github.com/ts468/seabios-tpm


I am facing an issue where WIndows 10 guest device manager reports TPM 
status as @

The device status is "The device cannot find enough free resources it can use (Code 12)"#

On browsing I found this page 
  @https://bugzilla.redhat.com/show_bug.cgi?id=1281413" that reports 
exactly the same problem and the resolution patch @ 
https://bugzilla.redhat.com/attachment.cgi?id=1137166​ .


I applied the patch on the code and verified with debug trace that the 
patch code does executes.


But, I am still observingthe sameissue on Win 10 guest and on using 
ACPIdump utility in Windows guest I canstill see"IRQ5 and IRQNoFlags" in 
the ssdt.dsl code.

  Device (ISA.TPM)
{
Name (_HID, EisaId ("PNP0C31"))  // _HID: Hardware ID
Name (_STA, 0x0F)  // _STA: Status
Name (_CRS, ResourceTemplate ()  // _CRS: Current Resource Settings
{
Memory32Fixed (ReadWrite,
0xFED40000,         // Address Base
0x00005000,         // Address Length
)
IRQNoFlags ()
{5}
})



I am bit confused, from my understanding, its the QEMU that builds the 
SSDT table and I can also verify it from the logs. But somehow guest is 
getting the old ACPI values for TPM which is not acceptable to Windows.

Just to be sure, I also verified the SeaBIOS code and couldn't find any 
link to this table.


Here is the patch that I applied based on the link above:


if (misc->tpm_version != TPM_VERSION_UNSPEC) {
          ACPI_BUILD_DPRINTF("TPM: add MMIO\n");
          dev = aml_device("TPM");
          aml_append(dev, aml_name_decl("_HID", aml_eisaid("PNP0C31")));
          aml_append(dev, aml_name_decl("_STA", aml_int(0xF)));
          crs = aml_resource_template();
          aml_append(crs, aml_memory32_fixed(TPM_TIS_ADDR_BASE,
                     TPM_TIS_ADDR_SIZE, AML_READ_WRITE));
          aml_append(dev, aml_name_decl("_CRS", crs));
          aml_append(sb_scope, dev);
      }
aml_append(ssdt, sb_scope);

logs once I start qemu:

CPI_BUILD: init ACPI tables
ACPI_BUILD: TPM: add MMIO
ACPI_BUILD: init ACPI tables
ACPI_BUILD: TPM: add MMIO

tpm_tis:  read.4(00000f00) = 00011014
tpm_tis: write.1(00000008) = 00000000
tpm_tis:  read.1(00000000) = 00000081

Commands to start vTPM:
swtpm_cuse -M 260 -m 1 -n vtpm0

qemu-system-x86_64 -enable-kvm -m 1024 -boot d -bios bios.bin -boot 
menu=on -tpmdev cuse-tpm,id=tpm0,path=/dev/vtpm0 -device 
tpm-tis,tpmdev=tpm0 win.img

Please suggest if I am missing anything .

Thanks
Anshul Makkar

             reply	other threads:[~2017-04-18 17:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-18 17:42 anshul makkar [this message]
2017-04-18 18:46 ` [Qemu-devel] CUSE-TPM : Win 10 reports TPM device doesn't have sufficient resources Stefan Berger
2017-04-21  8:03   ` Anshul Makkar

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=152817b5-89cf-14fe-d83a-bb5c8d748c90@citrix.com \
    --to=anshul.makkar@citrix.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanb@us.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).