From: Kelvin Middleton <kelvin.middleton@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1716132] [NEW] Win 10 bitlocker won't initialise pass-through TPM
Date: Sat, 09 Sep 2017 14:05:24 -0000 [thread overview]
Message-ID: <150496592440.23639.12760780482468469571.malonedeb@wampee.canonical.com> (raw)
Public bug reported:
All stock Ubuntu Zesty, Win10Pro KVM guest configured with OVMF and Q35.
My host has an ASRock Z97 Extreme 6 board with a TPM header which is
populated with v1.2 complaint device.
Testing in my host the TPM device is function, I can tpm_takeownership
and tpm_clear successfully and similar testing by passing the device
through to a linux guest also succeeds.
However using Bitlocker in Windows 10 Pro release 1703 Windows advises
it cannot "Prepare" the device which I take to mean it cannot take
ownership of it. I believe this to be related to Windows inability to
view the TCG Event Log which is evidenced in the below 2 screencaps,
however I'm no expert.
https://s26.postimg.org/vter35eh5/Screenshot_20170907_114644.png
https://s26.postimg.org/klo854qyx/Screenshot_20170909_143841.png
I've also tested the scenario with qemu 2.10 which provided the exact
same results. The only difference in the test setup is that I had to
make the guest boot with SeaBios instead of OVMF. (Windows wouldn't
boot with OVMF with the boot manager giving me an error pointing to a
BCD issue. Researching this it seemed related to an old ACPI problem, I
believe this unrelated to my TPM issue so will do more research and
raise a separate bug for this if needed.)
Happy to provide further configurations and build logs as necessary so
please advise me what is needed.
Lastly for background reading. I've been trying to get TPM passthrough
working with Windows for a long time now and have hit several different
issues which I believe have been addressed by both code maturity in Qemu
but also in Windows releases. An earlier bug report can be found here
(https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1615722) which
concludes advising me to raise this new/separate issue.
Thanks in advance,
Kelvin
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1716132
Title:
Win 10 bitlocker won't initialise pass-through TPM
Status in QEMU:
New
Bug description:
All stock Ubuntu Zesty, Win10Pro KVM guest configured with OVMF and
Q35. My host has an ASRock Z97 Extreme 6 board with a TPM header
which is populated with v1.2 complaint device.
Testing in my host the TPM device is function, I can tpm_takeownership
and tpm_clear successfully and similar testing by passing the device
through to a linux guest also succeeds.
However using Bitlocker in Windows 10 Pro release 1703 Windows advises
it cannot "Prepare" the device which I take to mean it cannot take
ownership of it. I believe this to be related to Windows inability to
view the TCG Event Log which is evidenced in the below 2 screencaps,
however I'm no expert.
https://s26.postimg.org/vter35eh5/Screenshot_20170907_114644.png
https://s26.postimg.org/klo854qyx/Screenshot_20170909_143841.png
I've also tested the scenario with qemu 2.10 which provided the exact
same results. The only difference in the test setup is that I had to
make the guest boot with SeaBios instead of OVMF. (Windows wouldn't
boot with OVMF with the boot manager giving me an error pointing to a
BCD issue. Researching this it seemed related to an old ACPI problem,
I believe this unrelated to my TPM issue so will do more research and
raise a separate bug for this if needed.)
Happy to provide further configurations and build logs as necessary so
please advise me what is needed.
Lastly for background reading. I've been trying to get TPM
passthrough working with Windows for a long time now and have hit
several different issues which I believe have been addressed by both
code maturity in Qemu but also in Windows releases. An earlier bug
report can be found here
(https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1615722) which
concludes advising me to raise this new/separate issue.
Thanks in advance,
Kelvin
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1716132/+subscriptions
next reply other threads:[~2017-09-09 14:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-09 14:05 Kelvin Middleton [this message]
2017-09-11 15:44 ` [Qemu-devel] [Bug 1716132] [NEW] Win 10 bitlocker won't initialise pass-through TPM Stefan Berger
2020-11-09 18:32 ` [Bug 1716132] " Thomas Huth
2021-01-09 4:17 ` Launchpad Bug Tracker
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=150496592440.23639.12760780482468469571.malonedeb@wampee.canonical.com \
--to=kelvin.middleton@gmail.com \
--cc=1716132@bugs.launchpad.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.