From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org, "Yanan Wang" <wangyanan55@huawei.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Zhao Liu" <zhao1.liu@intel.com>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Eduardo Habkost" <eduardo@habkost.net>
Subject: Re: [PULL 0/5] Firmware 20241114 patches
Date: Thu, 14 Nov 2024 11:10:11 +0000 [thread overview]
Message-ID: <ZzXak8gl-IksvLkQ@redhat.com> (raw)
In-Reply-To: <20241114110101.44322-1-kraxel@redhat.com>
On Thu, Nov 14, 2024 at 12:00:56PM +0100, Gerd Hoffmann wrote:
> The following changes since commit f0a5a31c33a8109061c2493e475c8a2f4d022432:
>
> Update version for v9.2.0-rc0 release (2024-11-13 21:44:45 +0000)
>
> are available in the Git repository at:
>
> https://gitlab.com/kraxel/qemu.git tags/firmware-20241114-pull-request
>
> for you to fetch changes up to 5916a3b20fdbfbfc2f987f1121e945100c8c3cd2:
>
> x86/loader: add -shim option (2024-11-14 11:55:39 +0100)
>
> ----------------------------------------------------------------
> loader: fix efi binary loading via -kernel
> loader: support secure boot verification with direct kernel boot
Hard feature freeze was two days ago, so I would have thought
the new secure boot feature should wait until 10.0 cycle ?
Their commits say they depend on new OVMF features and we've
not updated the OVMF binaries in this cycle, so do we even
have the OVMF feature needed for this to work[1] ?
With regards,
Daniel
[1] admittedly not an issue for distros packaging ovmf separately
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2024-11-14 11:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 11:00 [PULL 0/5] Firmware 20241114 patches Gerd Hoffmann
2024-11-14 11:00 ` [PULL 1/5] vl: fix qemu_validate_options() indention Gerd Hoffmann
2024-11-14 11:00 ` [PULL 2/5] x86/loader: only patch linux kernels Gerd Hoffmann
2024-11-14 11:00 ` [PULL 3/5] x86/loader: read complete kernel Gerd Hoffmann
2024-11-14 11:01 ` [PULL 4/5] x86/loader: expose unpatched kernel Gerd Hoffmann
2024-11-14 11:01 ` [PULL 5/5] x86/loader: add -shim option Gerd Hoffmann
2024-11-14 11:10 ` Daniel P. Berrangé [this message]
2024-11-14 11:33 ` [PULL 0/5] Firmware 20241114 patches Gerd Hoffmann
2024-11-15 10:09 ` Peter Maydell
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-all 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=ZzXak8gl-IksvLkQ@redhat.com \
--to=berrange@redhat.com \
--cc=eduardo@habkost.net \
--cc=kraxel@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=wangyanan55@huawei.com \
--cc=zhao1.liu@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.