bug#35380: disk-image fails to install efi grub

[Marius Bakke <mbakke@fastmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1839 bytes --]

rendaw <7e9wc56emjakcm@s.rendaw.me> writes:

> On 5/4/19 12:10 AM, Marius Bakke wrote:
>> rendaw <7e9wc56emjakcm@s.rendaw.me> writes:
>>
>>> On 5/3/19 7:17 AM, Marius Bakke wrote:
>>>> That means you can't just take an operating system hard drive from one
>>>> EFI system to another.
>>> I'm absolutely not an expert on UEFI, and it's likely I'm
>>> misinterpreting some of the more subtle points you wrote, but do you
>>> have more information on the NVRAM restriction?  I've found a fair
>>> amount of references to making secure boot and UEFI capable media (USB
>>> and CD) around the web so I'm surprised it's not possible to make a
>>> portable UEFI image.  Wouldn't that make it difficult to install UEFI
>>> bootloaders on blank systems?
>> To clarify: "grub-efi" will not work to make a portable UEFI
>> installation.  For that you need "grub-mkstandalone" and place the
>> resulting executable in "/efi/boot/bootx64.efi" on your EFI System
>> Partition, like Guix does for disk images:
>> <https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/build/vm.scm#n399>.
>>
>> It would be nice to make this procedure more generally accessible.
>> Perhaps create a (grub-standalone-bootloader ...) procedure, similar to
>> (grub-efi-bootloader)?   Then it can be used to create portable EFI
>> systems straight from your config.scm.
>>
>> Would you like to give it a go?
> Ah thanks!  I was indeed misunderstanding some of the subtleties in your
> previous post, and thanks for the pointers.  Depending on how
> straightforward it is I might try my hand implementing it, time
> permitting, but it probably wouldn't be for at least a month due to
> other priorities.

Right, no worries!  Improving the EFI support in Guix has been on my
TODO list for a couple of years now, so it's not very urgent ;-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]