From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mx.groups.io with SMTP id smtpd.web11.67793.1673257792969070384 for ; Mon, 09 Jan 2023 01:49:53 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=fLnYqUOW; spf=pass (domain: redhat.com, ip: 170.10.129.124, mailfrom: osteffen@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1673257792; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=G0Gx3uv2LyTihgNkBobxxIf+lZ4gepn0FVjYZqzsDSA=; b=fLnYqUOWStpcSthnSiMWA3eTPuBWzGkUikZJ+MgiQ/jZLsq+AQ5nGJqEer3ARnyApulLKl YLMBHSSV9kDCiKU7uer6b1RDrucyJSfZtypFp5D96TAKiaXQL0KDjVEgvnsiHvt+pjhhQo ybOsWN/D5/Pjb98Rkvnoct0itmwyMo8= Received: from mail-lj1-f198.google.com (mail-lj1-f198.google.com [209.85.208.198]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-313-7PJDWlFcMBmbBFRs9gahwg-1; Mon, 09 Jan 2023 04:49:50 -0500 X-MC-Unique: 7PJDWlFcMBmbBFRs9gahwg-1 Received: by mail-lj1-f198.google.com with SMTP id g5-20020a2ea4a5000000b0027fc755957eso1758605ljm.22 for ; Mon, 09 Jan 2023 01:49:50 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=G0Gx3uv2LyTihgNkBobxxIf+lZ4gepn0FVjYZqzsDSA=; b=Z4rRYjcmRDojiIGM42S17mMzPCXpEKBEbmyItNf3iehsrgLAXTpYbtOBoOIj/nB9/0 5JZBAyHhUuRAShG5hsERg/eybBn50mYd5DSwdjTVeJyUGuAr+M6hPMRXETi1coAos7BK oNwHDIBEKJwGHQdaG0ONbK3ReP6ippnqvQypl6ZAh4qPd/BrE/1s+BTWScCXayJvMDRb AwwPoilqbfqEd5/u/Kzj4Pp7wdV6MKOr4iYYMDLKBpPFF9jdClEhdgVsdur9LdzMFpCy /EHTg00MGYvPsYGXEwtslK65ZWCq+kD5oDIiOGN6u5Nj4lpnf25f4syk7kkZPrwTB+DJ sF+w== X-Gm-Message-State: AFqh2krPN1VjJYPEtcf5vBzZTK7duzte8sYWj5G0mqoGpaQUHij8ygr0 1eGliiX4fRyV5bKK/bAXW4OT6E11wWiX4/wddnx0GOQHx990F3BZ4kGz0evEvdKCsdg4zsWS+gR /ZQ2ilTK9YEqLRe1EqVtsqxuDgJ9bYQ== X-Received: by 2002:a05:6512:23a9:b0:4bb:70b2:6f4a with SMTP id c41-20020a05651223a900b004bb70b26f4amr7270356lfv.1.1673257788909; Mon, 09 Jan 2023 01:49:48 -0800 (PST) X-Google-Smtp-Source: AMrXdXtkKoG9IddWzSO/TnuG5mkkXE5F8QhipgTt/U4F/lXofHo+Z29BHb5MgMQuD6md+Erw9AEp08+bgiaRYRGuxBA= X-Received: by 2002:a05:6512:23a9:b0:4bb:70b2:6f4a with SMTP id c41-20020a05651223a900b004bb70b26f4amr7270342lfv.1.1673257788628; Mon, 09 Jan 2023 01:49:48 -0800 (PST) MIME-Version: 1.0 References: <20230104151234.286030-1-lersek@redhat.com> <20230105131222.jx3ridl4eb73xn2a@sirius.home.kraxel.org> <20230105135211.jdletfnhvn3edjqi@sirius.home.kraxel.org> <9bbcf3b8-1ef6-398c-ac6f-1fac7036f843@redhat.com> <173772B56BF8C7B8.2132@groups.io> In-Reply-To: <173772B56BF8C7B8.2132@groups.io> From: "Oliver Steffen" Date: Mon, 9 Jan 2023 10:49:37 +0100 Message-ID: Subject: Re: [edk2-devel] [PATCH 0/1] OvmfPkg/PlatformInitLib: catch QEMU's CPU hotplug reg block regression To: Gerd Hoffmann , Laszlo Ersek Cc: devel@edk2.groups.io, Ard Biesheuvel , Brijesh Singh , Erdem Aktas , James Bottomley , Jiewen Yao , Jordan Justen , Min Xu , Sebastien Boeuf , Tom Lendacky X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: multipart/alternative; boundary="0000000000001c020e05f1d1b012" --0000000000001c020e05f1d1b012 Content-Type: text/plain; charset="UTF-8" On Thu, Jan 5, 2023 at 4:19 PM Oliver Steffen wrote: > Quoting Laszlo Ersek (2023-01-05 16:12:36) > > On 1/5/23 14:52, Gerd Hoffmann wrote: > > > On Thu, Jan 05, 2023 at 02:43:32PM +0100, Oliver Steffen wrote: > > >> Quoting Gerd Hoffmann (2023-01-05 14:12:22) > > >>> Not sure this is an option. Is nested virtualization supported in > azure > > >>> pipeline VMs? If so, is /dev/kvm passed into containers? > > >> > > >> I doubt it, but need to check. > > > > > >>> That requires updating the fedora containers though. I think they > are > > >>> at Fedora 35 still, which is EOL meanwhile, so no more updates ... > > >> > > >> Yes, it is Fedora 35, because we were (are?) not ready for gcc 12 yet. > > > > > > The gcc12 fix finally landed > (129404f6e4395008ac0045e7e627edbba2a1e064), > > > so yes, we are ready now. > > > > > >> Currently we are building Qemu is from scratch anyway (instead of > > >> using the Fedora 35 repo) becasue we needed a recent one, see > > >> > https://github.com/tianocore/containers/blob/main/Fedora-35/Dockerfile#L75 > > > > > > Alternative to self-compiling is using > > > https://fedoraproject.org/wiki/Virtualization_Preview_Repository > > > for a more recent qemu version. > > > > Ah, those options all sound great. I didn't expect it was possible to > > use self-built (or otherwise "externally sourced") QEMUs in CI! > > I would prefer the tar download since it is a rather long lived and > version-stable source. We a trying to pin down the version numbers the > most relevant tools so that they don't "run away"/update without > intent. > > I'll also check if we can run the CI with gcc 12. > Unfortunately, the EDK2 CI as a whole is not ready for gcc 12. RiscV64 builds fail: RiscV64/FlushCache.iiii:16: Error: unrecognized opcode `fence.i' Here we are hitting a downside of the approach of relying on distro-packages. -Oliver --0000000000001c020e05f1d1b012 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, Jan 5, 2023 at 4:19 PM Oliver Steffen <osteffen@redhat.com> wrote:
Quoting Laszlo Ersek (2023-01-05 16= :12:36)
> On 1/5/23 14:52, Gerd Hoffmann wrote:
> > On Thu, Jan 05, 2023 at 02:43:32PM +0100, Oliver Steffen wrote: > >> Quoting Gerd Hoffmann (2023-01-05 14:12:22)
> >>> Not sure this is an option.=C2=A0 Is nested virtualizatio= n supported in azure
> >>> pipeline VMs?=C2=A0 If so, is /dev/kvm passed into contai= ners?
> >>
> >> I doubt it, but need to check.
> >
> >>> That requires updating the fedora containers though.=C2= =A0 I think they are
> >>> at Fedora 35 still, which is EOL meanwhile, so no more up= dates ...
> >>
> >> Yes, it is Fedora 35, because we were (are?) not ready for gc= c 12 yet.
> >
> > The gcc12 fix finally landed (129404f6e4395008ac0045e7e627edbba2a= 1e064),
> > so yes, we are ready now.
> >
> >> Currently we are building Qemu is from scratch anyway (instea= d of
> >> using the Fedora 35 repo) becasue we needed a recent one, see=
> >> https://gith= ub.com/tianocore/containers/blob/main/Fedora-35/Dockerfile#L75
> >
> > Alternative to self-compiling is using
> > https://fedoraproject.org/= wiki/Virtualization_Preview_Repository
> > for a more recent qemu version.
>
> Ah, those options all sound great. I didn't expect it was possible= to
> use self-built (or otherwise "externally sourced") QEMUs in = CI!

I would prefer the tar download since it is a rather long lived and
version-stable source. We a trying to pin down the version numbers the
most relevant tools so that they don't "run away"/update with= out
intent.

I'll also check if we can run the CI with gcc 12.
= Unfortunately, the = EDK2 CI=C2=A0as a whole is not ready for gcc 12. RiscV64 builds fail:
=
=C2=A0 RiscV64/F= lushCache.iiii:16: Error: unrecognized opcode `fence.i'

=
Here we are hi= tting a downside of the approach of relying on distro-packages.

-Oliver
--0000000000001c020e05f1d1b012--