All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "Andrea Bolognani" <abologna@redhat.com>,
	qemu-devel@nongnu.org, "Kashyap Chamarthy" <kchamart@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Markus Armbruster" <armbru@redhat.com>
Subject: Re: [PATCH 2/2] docs/interop/firmware: Introduce extended syntax for FirmwareMappingMemory
Date: Tue, 6 Jan 2026 11:34:45 +0000	[thread overview]
Message-ID: <aVzzVZxZDWMDZjXs@redhat.com> (raw)
In-Reply-To: <aVzs_6lD5XJhCn0H@dobby.home.kraxel.org>

On Tue, Jan 06, 2026 at 12:28:38PM +0100, Gerd Hoffmann wrote:
>   Hi,
> 
> > > Maybe have separate json files describing the variable store template
> > > only, and expect libvirt searching for one in case the firmware
> > > descriptor has the 'host-uefi-vars' feature flag set?
> > 
> > Or just have the host-uefi-vars feature flag alone, and then libvirt
> > can just invoke virt-firmware in whatever way it needs to create the
> > json templates and not worry about providing any pre-defined json
> > files.  All the default microsoft CAs are ultimately embedded in
> > virt-firmware and spat out when given the right args.
> 
> Makes sense too, given that the long-term plan is to do that anyway to
> allow distro-specific varstore setups.  So doing that right from the
> start, only without the certificate configuration part which comes
> later, looks like good approach too.
> 
> BTW: virt-firmware-rs.rpm has a utility (virt-fw-vars-setup) which can
> do exactly that without pulling in python as dependency.
> 
> Question is how we enable/disable secure boot then ... 
> 
> One option would be to special-case the enrolled-keys feature for the
> host-uefi-vars.  A little bit hackish, but with the advantage that the
> switch would be transparent for libvirt users, existing xml syntax
> continues to work.

Currently the libvirt XML features are matched to firmware descriptor
features, but that's just an internal implementation detail for libvirt.
We can have our impl match XML features to virt-fw-var-setup flags
instead where appropriate for the firmware.

> 
> Another option would be to add xml syntax for varstore setup, which will
> be needed anyway in the future for the custom certificate setup.
> 
> take care,
>   Gerd
> 

With regards,
Daniel
-- 
|: 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 :|



  reply	other threads:[~2026-01-06 11:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-28 23:26 [PATCH 0/2] docs/interop/firmware: Introduce extended syntax for FirmwareMappingMemory Andrea Bolognani
2025-12-28 23:26 ` [PATCH 1/2] docs/interop/firmware: Rename FirmwareFormat to FirmwareFlashFormat Andrea Bolognani
2026-01-05  8:40   ` Michal Prívozník
2025-12-28 23:26 ` [PATCH 2/2] docs/interop/firmware: Introduce extended syntax for FirmwareMappingMemory Andrea Bolognani
2026-01-05 14:40   ` Daniel P. Berrangé
2026-01-06 10:13     ` Gerd Hoffmann
2026-01-06 10:36       ` Daniel P. Berrangé
2026-01-06 11:28         ` Gerd Hoffmann
2026-01-06 11:34           ` Daniel P. Berrangé [this message]
2025-12-29  1:34 ` [PATCH 0/2] " Andrea Bolognani
2026-01-05 14:11 ` Gerd Hoffmann

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=aVzzVZxZDWMDZjXs@redhat.com \
    --to=berrange@redhat.com \
    --cc=abologna@redhat.com \
    --cc=armbru@redhat.com \
    --cc=kchamart@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /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.