Hi, > > grub does not properly integrate with EFI, i.e. it brings its own set of > > filesystem drivers but does not register them as EFI protocols. So on a > > typical fedora install where /boot is xfs grub itself can access /boot > > but anything loaded by grub can not. > > We currently default to ext4, not XFS for /boot, though we do have EFI > filesystem drivers we could ship for btrfs, ext4, and xfs for those cases.
Yes, someone took the grub drivers and turned them into efi filesystem drivers. That is IMHO a rather crude workaround for grub mostly ignoring EFI. Also these drivers are (a) not installed by default and (b) lack a secure boot signature, so they do not really change the picture. edk2 has a ext4 driver too (see edk2-ext4.rpm). I could roll that one into the OVMF firmware. Would get us past the secure boot issue as binaries included in the firmware image are trusted even without signature. Obvious problem is that this would work for virtual machines only, and I suspect openQA will not appreciate VM behavior derive from physical hardware behavior like that ... take care, Gerd -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
