From: "Gerd Hoffmann" <kraxel@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: devel@edk2.groups.io, Ard Biesheuvel <ardb+tianocore@kernel.org>,
Brijesh Singh <brijesh.singh@amd.com>,
Erdem Aktas <erdemaktas@google.com>,
James Bottomley <jejb@linux.ibm.com>,
Jiewen Yao <jiewen.yao@intel.com>,
Jordan Justen <jordan.l.justen@intel.com>,
Min Xu <min.m.xu@intel.com>,
Sebastien Boeuf <sebastien.boeuf@intel.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
Oliver Steffen <osteffen@redhat.com>
Subject: Re: [PATCH 0/1] OvmfPkg/PlatformInitLib: catch QEMU's CPU hotplug reg block regression
Date: Thu, 5 Jan 2023 14:12:22 +0100 [thread overview]
Message-ID: <20230105131222.jx3ridl4eb73xn2a@sirius.home.kraxel.org> (raw)
In-Reply-To: <20230104151234.286030-1-lersek@redhat.com>
Hi,
> So I'm not proposing to merge this immediately; something must be fixed
> first:
>
> - use KVM in the CI env, or
Not sure this is an option. Is nested virtualization supported in azure
pipeline VMs? If so, is /dev/kvm passed into containers?
> - delay this patch until my QEMU fix is merged, and a new release is
> made, and the new QEMU release is packaged by the distros, and the new
> distro packages are picked up by github.com CI.
Well. There is the pending patch series by Oliver to switch over CI to
use containers, and build using fedora container images. Putting the
fix on fast track and backport the fix to the fedora packages should be
in the cards, which should get us a working qemu quickly.
That requires updating the fedora containers though. I think they are
at Fedora 35 still, which is EOL meanwhile, so no more updates ...
Oliver?
CI team?
take care,
Gerd
next prev parent reply other threads:[~2023-01-05 13:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 15:12 [PATCH 0/1] OvmfPkg/PlatformInitLib: catch QEMU's CPU hotplug reg block regression Laszlo Ersek
2023-01-04 15:12 ` [PATCH 1/1] " Laszlo Ersek
2023-01-05 13:12 ` Gerd Hoffmann
2023-01-04 23:34 ` [edk2-devel] [PATCH 0/1] " Michael D Kinney
2023-01-05 5:39 ` Guo, Gua
2023-01-05 15:15 ` Laszlo Ersek
2023-01-05 15:17 ` Laszlo Ersek
2023-01-05 13:12 ` Gerd Hoffmann [this message]
2023-01-05 13:43 ` Oliver Steffen
2023-01-05 13:52 ` Gerd Hoffmann
2023-01-05 15:12 ` Laszlo Ersek
2023-01-05 15:18 ` Oliver Steffen
[not found] ` <173772B56BF8C7B8.2132@groups.io>
2023-01-09 9:49 ` [edk2-devel] " Oliver Steffen
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=20230105131222.jx3ridl4eb73xn2a@sirius.home.kraxel.org \
--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