[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [xen-4.12-testing bisection] complete test-amd64-i386-xl-qemuu-ovmf-amd64

  • To: Jan Beulich <jbeulich@xxxxxxxx>
  • From: Anthony PERARD <anthony.perard@xxxxxxxxxx>
  • Date: Mon, 23 Aug 2021 10:33:25 +0100
  • Authentication-results: esa6.hc3370-68.iphmx.com; dkim=none (message not signed) header.i=none
  • Cc: Ian Jackson <iwj@xxxxxxxxxxxxxx>, osstest service owner <osstest-admin@xxxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Mon, 23 Aug 2021 09:33:35 +0000
  • Ironport-hdrordr: A9a23:mPruz6MTPMiHOsBcTs+jsMiBIKoaSvp037BL7SxMoHluGfBw+P rAoB1273HJYVQqOE3I6OrgBEDoexq1n/NICOIqTNSftWfdyQ6VBbAnwYz+wyDxXw3Sn9QtsZ uIqpIOauHNMQ==
  • Ironport-sdr: yyLdlr/SNROMQXTYXTS5rlSNSroHXNPEzbFLlBcBzUgQxKiK9+oRo5sZrhhctEHECs2GwcBVw6 +Bln1IMCWOWpQA11h4Pi5dWHqO0xuQr+NAeEqdgCIF1teXzumMtp4HGgwnIMq9l47Omv5Ye6iW FUYaHRtm1XCmbRXMWkpqQ7xREiRrUu+SfxfX1CowHk5v/pECrO2Y5MVQi9SRsoyUe7z87tfa6u NEn4CGdJoHhvk3ARQyeBwdLbtrqOyJcIHmbJLCrWz4SS+wWn5p8EETAy49pURUxGSavmsyoe0R ZjI0ol2biqVABrfiAT2F/E3z
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On Mon, Aug 23, 2021 at 09:07:32AM +0200, Jan Beulich wrote:
> On 23.08.2021 02:40, osstest service owner wrote:
> >   commit d06eb2d1d9dd8da1ed84bd08c5783a0264fe2b64
> >   Author: Laszlo Ersek <lersek@xxxxxxxxxx>
> >   Date:   Wed May 26 22:14:24 2021 +0200
> >   
> >       OvmfPkg/PlatformPei: remove Xen support
> Uniformly from 4.15 through to 4.12 (the latter of which shouldn't have
> been affected by whatever has been pulled in in the first place, given
> it's a security-only branch, but with the OVMF commit to use being
> hardcoded in ./Config.mk I don't really understand how a possible
> change to the OVMF tree could have affected this version) tests are
> now failing, everywhere with the above bisection result. Given that we
> want to get out releases from the 4.15 and 4.13 branches right after
> the batch of XSAs going public on Wednesday, something needs to be
> done about this pretty soon.
> Does osstest override ./Config.mk's choice? Albeit I guess even if it
> does that's not outright wrong, and instead it would be bad if the
> older versions wouldn't work anymore with an updated OVMF.

Yes, osstest uses "xen-tested-master" branch since c9d1e5896fe2
("cr-daily-branch: ovmf: "usually" use xen-tested-master") for stable

We are going to need to backport a commit from unstable. Either
    aad7b5c11d51 ("tools/firmware/ovmf: Use OvmfXen platform file is exist")
        (but has been reverted)
    81f291420238 ("tools/firmware/ovmf: Use OvmfXen platform file if exist and 
update OVMF")
        (but it also changes the version of ovmf pulled by default,
         which we probably don't want to change)

So I would suggest backporting aad7b5c11d51.


Anthony PERARD



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.