From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, jejb@linux.ibm.com
Cc: dovmurik@linux.vnet.ibm.com, Dov.Murik1@il.ibm.com,
ashish.kalra@amd.com, brijesh.singh@amd.com, tobin@ibm.com,
david.kaplan@amd.com, jon.grimm@amd.com, thomas.lendacky@amd.com,
frankeh@us.ibm.com,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
Jordan Justen <jordan.l.justen@intel.com>,
Ard Biesheuvel <ard.biesheuvel@arm.com>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
Michael Kinney <michael.d.kinney@intel.com>,
Sean Brogan <sean.brogan@microsoft.com>
Subject: Re: [edk2-devel] [PATCH 0/2] Update SevSecret API to work for TDX
Date: Thu, 17 Dec 2020 21:00:04 +0100 [thread overview]
Message-ID: <993d89eb-e0d3-ab81-4faa-7c637e7a0639@redhat.com> (raw)
In-Reply-To: <0de76b37-1914-cb97-ed5f-70141de3bc8a@redhat.com>
On 12/17/20 20:23, Laszlo Ersek wrote:
> On 12/17/20 19:43, Laszlo Ersek wrote:
>
>> I tried merging this:
>>
>> https://github.com/tianocore/edk2/pull/1235
>>
>> but the Ubuntu builds all failed. I've checked two logs:
>>
>> https://dev.azure.com/tianocore/edk2-ci/_build/results?buildId=16967&view=logs&j=cf2d8b26-a21c-5c68-abf4-b944c123e462&t=5ffbbe5c-1d3a-55f5-5ef3-8a0ef80d76a1&l=184
>> https://dev.azure.com/tianocore/edk2-ci/_build/results?buildId=16968&view=logs&j=47cf355a-6eb4-51a8-46a8-ff4028bfcac0&t=beedef5d-00d0-5a8c-fa35-57d7319988c2&l=182
>>
>> They say,
>>
>> INFO - /bin/sh: 1: qemu-system-aarch64: not found
>> INFO - /bin/sh: 1: qemu-system-x86_64: not found
>
> The "Install qemu" tasks earlier seem to complete:
>
> https://dev.azure.com/tianocore/edk2-ci/_build/results?buildId=16967&view=logs&j=cf2d8b26-a21c-5c68-abf4-b944c123e462&t=a5c654c1-e049-5a30-61a9-da81b8ec031f
> https://dev.azure.com/tianocore/edk2-ci/_build/results?buildId=16968&view=logs&j=47cf355a-6eb4-51a8-46a8-ff4028bfcac0&t=9a629c6e-a36d-5733-3aff-19ed2a42cf75
>
> However, the qemu "4.2-3ubuntu6.10" package is a dummy package:
>
> https://packages.ubuntu.com/focal/qemu
>
> and as shown under the link, it has no dependency on the packages with the actual qemu executables. So the latter do not get pulled in.
>
> (Even the logs make that clear: "Need to get 14.3 kB of archives" -- obviously, a real QEMU won't fit in that, and no other packages get pulled in).
>
> The meta-package that pulls in all system emulators is called "qemu-system":
>
> https://packages.ubuntu.com/focal/qemu-system
>
> What I don't understand at this point is how the CI scripts could work previously.
>
> ... Aha! I do understand it now. Look at one of the last successful PRs:
>
> https://github.com/tianocore/edk2/pull/1232
>
> The CI logs contain this message:
>
> "##[warning]Ubuntu-latest pipelines will use Ubuntu-20.04 soon. For more details, see https://github.com/actions/virtual-environments/issues/1816"
>
> So let's check out:
>
> https://github.com/actions/virtual-environments/issues/1816
>
> Okay... so it looks like I'm the victim of "Ubuntu-latest" switching to 20.04 ("focal") from 18.04 ("bionic"). Compare the "qemu" package in both:
>
> https://packages.ubuntu.com/bionic/qemu
> https://packages.ubuntu.com/focal/qemu
>
> In the former, qemu depends on qemu-system (which depends further on the actual emulator subpackages), in the latter, qemu doesn't depend on anything.
>
> According to <https://github.com/actions/virtual-environments/issues/1816>, we could change:
>
> .azurepipelines/Ubuntu-GCC5.yml: vm_image: 'ubuntu-latest'
> .azurepipelines/Ubuntu-PatchCheck.yml: vmImage: 'ubuntu-latest'
> ArmVirtPkg/PlatformCI/.azurepipelines/Ubuntu-GCC5.yml: vm_image: 'ubuntu-latest'
> EmulatorPkg/PlatformCI/.azurepipelines/Ubuntu-GCC5.yml: vm_image: 'ubuntu-latest'
> OvmfPkg/PlatformCI/.azurepipelines/Ubuntu-GCC5.yml: vm_image: 'ubuntu-latest'
>
> to "ubuntu-18.04". But perhaps we should change:
>
> ArmVirtPkg/PlatformCI/.azurepipelines/Ubuntu-GCC5.yml: - bash: sudo apt-get install qemu
> OvmfPkg/PlatformCI/.azurepipelines/Ubuntu-GCC5.yml: - bash: sudo apt-get install qemu
>
> to "qemu-system", instead.
Well, no. I've just tried that:
https://github.com/tianocore/edk2/pull/1236
and we have two problems with it:
(1) the emulator is now available, but it crashes:
https://dev.azure.com/tianocore/edk2-ci/_build/results?buildId=16975&view=logs&j=cf2d8b26-a21c-5c68-abf4-b944c123e462&t=5ffbbe5c-1d3a-55f5-5ef3-8a0ef80d76a1
"INFO - Segmentation fault (core dumped)"
(2) in spite of this failure, the mergify bot says, "All checks passed.
Auto close personal build." :/
So at the moment we can only go back to the 18.04LTS image. I'll try
that next.
Laszlo
next prev parent reply other threads:[~2020-12-17 20:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 1:41 [PATCH 0/2] Update SevSecret API to work for TDX James Bottomley
2020-12-16 1:41 ` [PATCH 1/2] OvmfPkg: Change SEV Launch Secret API to be UINT64 for base and size James Bottomley
2020-12-16 1:41 ` [PATCH 2/2] OvmfPkg/AmdSev/SecretDxe: make secret location naming generic James Bottomley
2020-12-16 8:27 ` Dov Murik
2020-12-16 16:53 ` James Bottomley
2020-12-17 0:25 ` Yao, Jiewen
2020-12-16 1:55 ` [PATCH 0/2] Update SevSecret API to work for TDX Yao, Jiewen
2020-12-17 18:43 ` [edk2-devel] " Laszlo Ersek
2020-12-17 19:23 ` Laszlo Ersek
2020-12-17 20:00 ` Laszlo Ersek [this message]
2020-12-18 10:49 ` Laszlo Ersek
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-list 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=993d89eb-e0d3-ab81-4faa-7c637e7a0639@redhat.com \
--to=devel@edk2.groups.io \
/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