Ubuntu
qemu package

  1. Bug #1615722
  2. Comment #10

Comment 10 for bug 1615722

Revision history for this message
Kelvin Middleton (kelvin-middleton) wrote :

Hi apologies for the radio silence.

I've since upgrade my host so I'm now testing on zesty with stock qemu at v2.8...

Have just retested with my guest Win10Pro @ v1703.

So the original problem of the guest tpm driver getting a resource conflict is not longer an issue as per my post #5 here.

However the new update since testing today is that Windows does now recognise the TPM device but will not allow me to take ownership. Screenshot of the guest view of the TPM (https://s26.postimg.org/vter35eh5/Screenshot_20170907_114644.png). I can't "Prepare the TPM" which is Windows speak for taking ownership and I am unsure why.

As part of today's testing I have cleared the TPM via the UEFI, re-enabled the TPM, booted into my zesty host and run tpm_selftest as well as tpm_takeownership successfully and subsequently tpm_clear which required a reboot to complete. I then went back into the UEFI, re-enabled the TPM and then tested in the guest but was unable to take ownership. As such I believe the TPM interaction with the host is functional but still some functionality is not being passed through to the qemu guest?