Integrating swtpm(as a software TPM) with OpenBMC on Qemu

[Sandeep Kumar]

TCS Confidential


Hi C,

Built the qemu from your branch. Few issues,

      $ ./qemu-system-arm -m 256 -M romulus-bmc -nographic -drive file=./obmc-phosphor-image-romulus.static.mtd,format=raw,if=mtd -net nic -net user,hostfwd=:127.0.0.1:2222-:22,hostfwd=:127.0.0.1:4443-:443,hostfwd=tcp:127.0.0.1:8880-:80,hostfwd=tcp:127.0.0.1:2200-:2200,hostfwd=udp:127.0.0.1:6623-:623,hostfwd=udp:127.0.0.1:6664-:664,hostname=qemu
      qemu-system-arm: -net user,hostfwd=:127.0.0.1:2222-:22,hostfwd=:127.0.0.1:4443-:443,hostfwd=tcp:127.0.0.1:8880-:80,hostfwd=tcp:127.0.0.1:2200-:2200,hostfwd=udp:127.0.0.1:6623-:623,hostfwd=udp:127.0.0.1:6664-:664,hostname=qemu: network backend 'user' is not compiled into this binary


I didn’t enable the slirp package I guess. So enabled it while running configure,

      $ ../configure --enable-slirp
      ........
      Run-time dependency slirp found: NO (tried pkgconfig)

      ../meson.build:681:2: ERROR: Dependency "slirp" not found, tried pkgconfig

      A full log can be found at /home/tcs/work/sandeep/measured_boot/ibm_qemu/qemu/build/meson-logs/meson-log.txt
      NOTICE: You are using Python 3.6 which is EOL. Starting with v0.62.0, Meson will require Python 3.7 or newer

      ERROR: meson setup failed


I have already installed slirp locally, but still getting the above error.

Please do let let me know your comments.

Thanks,
Sandeep.

-----Original Message-----
From: Cédric Le Goater <clg at kaod.org>
Sent: Wednesday, April 12, 2023 8:43 PM
To: Sandeep Kumar <sandeep.pkumar at tcs.com>; openbmc at lists.ozlabs.org; Ninad Palsule <ninad at linux.ibm.com>; Joel Stanley <jms at jms.id.au>; Andrew Jeffery <andrew at aj.id.au>
Subject: Re: Integrating swtpm(as a software TPM) with OpenBMC on Qemu

"External email. Open with Caution"

On 4/12/23 07:12, Sandeep Kumar wrote:
>   TCS Confidential
>
> Hi C,
>
> Thanks for sharing the info.  We have started working on it. Could you please point to the exact patches that needs to be applied on openBMC Qemu ? There are too many patches to choose from.

Just use my branch for now. OpenBMC QEMU is outdated.
We'll resync when 8.0 is out

Thanks,

C.

>
> Thanks,
> Sandeep.
>
> -----Original Message-----
> From: Cédric Le Goater <clg at kaod.org<mailto:clg at kaod.org>>
> Sent: Wednesday, April 5, 2023 7:25 PM
> To: Sandeep Kumar <sandeep.pkumar at tcs.com<mailto:sandeep.pkumar at tcs.com>>; openbmc at lists.ozlabs.org<mailto:openbmc at lists.ozlabs.org>;
> Ninad Palsule <ninad at linux.ibm.com<mailto:ninad at linux.ibm.com>>; Joel Stanley <jms at jms.id.au<mailto:jms at jms.id.au>>;
> Andrew Jeffery <andrew at aj.id.au<mailto:andrew at aj.id.au>>
> Subject: Re: Integrating swtpm(as a software TPM) with OpenBMC on Qemu
>
> "External email. Open with Caution"
>
> Hello,
>
> On 4/5/23 14:48, Sandeep Kumar wrote:
>> TCS Confidential
>>
>>
>> Hi,
>>
>> Trying to see how to get swtpm working as a virtual TPM and connect to openBMC on QEMU. How do we achieve this? Main idea is to get this working and make secure boot through the virtual TPM(swtpm).
>
> Ninad did a nice how to :
>
>
> https://lore.kernel.org/qemu-devel/20230331161319.2250334-4-ninadpalsu
> le at us.ibm.com/<mailto:le at us.ibm.com/>
>
> If you want to try, the patches are on this branch :
>
>     https://github.com/legoater/qemu/commits/aspeed-8.0
>
> and they should reach the QEMU OpenBMC repo at some point in time.
>
>
> Joel also provided a simple test case :
>
>
> https://lore.kernel.org/qemu-devel/20230328120844.190914-1-joel@jms.id
> .au/
>
> using the ast2600-evb machine.
>
> Cheers,
>
> C.
>
>   TCS Confidential
> =====-----=====-----=====
> Notice: The information contained in this e-mail message and/or
> attachments to it may contain confidential or privileged information.
> If you are not the intended recipient, any dissemination, use, review,
> distribution, printing or copying of the information contained in this
> e-mail message and/or attachments to it are strictly prohibited. If
> you have received this communication in error, please notify us by
> reply e-mail or telephone and immediately and permanently delete the
> message and any attachments. Thank you
>
>




TCS Confidential
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20230418/56812ccd/attachment-0001.htm>