From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Stefan Berger <stefanb@linux.ibm.com>, qemu-devel@nongnu.org
Cc: eric.auger@redhat.com,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>
Subject: Re: Windows on ARM64 not able to use attached TPM 2
Date: Mon, 2 Aug 2021 11:04:59 +0200 [thread overview]
Message-ID: <5ef559fa-c996-ba42-b9f0-416c7de661c8@redhat.com> (raw)
In-Reply-To: <f288d6fb-4286-252c-1e3c-f92076dbc51e@linux.ibm.com>
Cc'ing Marc-André who is your EDK2 co-maintainer.
On 8/1/21 2:28 AM, Stefan Berger wrote:
> Hello!
>
> I maintain the TPM support in QEMU and the TPM emulator (swtpm). I have
> a report from a user who would like to use QEMU on ARM64 (aarch64) with
> EDK2 and use an attached TPM 2 but it doesn't seem to work for him. We
> know that Windows on x86_64 works with EDK2 and can use an attached TPM
> 2 (using swtpm). I don't have an aarch64 host myself nor a Microsoft
> account to be able to access the Windows ARM64 version, so maybe someone
> here has the necessary background, credentials, and hardware to run QEMU
> on using kvm to investigate what the problems may be due to on that
> platform.
>
> https://github.com/stefanberger/swtpm/issues/493
>
> On Linux it seems to access the TPM emulator with the normal tpm_tis
> driver.
>
> Regards,
>
> Stefan
>
>
>
next prev parent reply other threads:[~2021-08-02 9:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-01 0:28 Windows on ARM64 not able to use attached TPM 2 Stefan Berger
2021-08-02 9:04 ` Philippe Mathieu-Daudé [this message]
2021-08-02 9:51 ` Eric Auger
2021-08-02 12:09 ` Ard Biesheuvel
2021-08-02 13:21 ` Philippe Mathieu-Daudé
2021-08-02 13:31 ` Philippe Mathieu-Daudé
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=5ef559fa-c996-ba42-b9f0-416c7de661c8@redhat.com \
--to=philmd@redhat.com \
--cc=eric.auger@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanb@linux.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).