On Fri, Mar 14, 2025 at 8:47 PM Jörg Rödel <j...@8bytes.org> wrote: > > On Fri, Mar 14, 2025 at 03:08:43PM +0100, Gerd Hoffman wrote: > > If your input firmware image already is an IGVM (say coconut), what is > > supposed to happen? > > The COCONUT igvmbuilder has the ability to take another IGVM file as > input and add its directive and contents to the output file. This is > needed for the Hyper-V firmware, which is also provided as an IGVM file. > I think it can also make changes when processing an input IGVM, like > changing the VMPL of a VMSA. > > This can be extended to cover more use-cases, e.g. like direct-boot of a > linux kernel with initrd and command-line.
Have we considered how IGVM will be deployed in the FUKI case? I have always assumed that UKI would be the right means for this. For edk2 for example, we are implementing support in UKI. Hopefully the same can apply for IGVM.
