From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46192) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dC1Gy-0003dL-B4 for guix-patches@gnu.org; Sat, 20 May 2017 06:06:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dC1Gt-0006vk-8V for guix-patches@gnu.org; Sat, 20 May 2017 06:06:08 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:53354) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dC1Gt-0006vg-52 for guix-patches@gnu.org; Sat, 20 May 2017 06:06:03 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dC1Gs-0003gz-Ty for guix-patches@gnu.org; Sat, 20 May 2017 06:06:02 -0400 Subject: bug#26815: [PATCH v4 3/3] vm: Add UEFI loader to disk images. Resent-Message-ID: From: Marius Bakke In-Reply-To: <87a8673m4n.fsf@gmail.com> References: <87r2zoygoi.fsf@gnu.org> <20170517110522.18106-1-mbakke@fastmail.com> <20170517110522.18106-3-mbakke@fastmail.com> <87ziebtbph.fsf@gnu.org> <877f1ecf00.fsf@fastmail.com> <8737c2cbm5.fsf@fastmail.com> <871srlankf.fsf@gnu.org> <87k25cvn49.fsf@fastmail.com> <87pof4agte.fsf@gmail.com> <87h90gvhz3.fsf@fastmail.com> <87a8673m4n.fsf@gmail.com> Date: Sat, 20 May 2017 12:05:41 +0200 Message-ID: <87r2zjg7wq.fsf@fastmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Mathieu Othacehe Cc: 26815-done@debbugs.gnu.org --=-=-= Content-Type: text/plain Mathieu Othacehe writes: > Hi Marius, > >> I plan to make a generic "grub-standalone" variant. Will try to fit it >> into the new bootloader API. The regular grub-efi variant won't cut it >> because it can't update EFI variables on the target system, so we need >> the "self-contained" grub snapshot generated by grub-mkstandalone(1). >> >> Also, the normal configuration file doesn't work with it, but a minimal >> config that loads the real one at boot is okay. Not sure why! > > Ok, but don't we need to do it on system reconfigure too ? Using "grub-mkstandalone" as an everyday bootloader is not a priority, though it would be nice to support that too. It doesn't make much sense to use that instead of "grub-efi" on a native system, but it can also generate e.g. standalone PXE, u-boot and yeelong loaders. >> On a related topic: The "device" field for grub-efi is a noop; >> `grub-install` looks for "/boot/efi" only (or "--efi-directory"). >> Currently the example uses the ESP for "device", but it should not have >> to be set. Not sure what to do about it, ideas? > > The "device" field of defaults to #f so maybe you can skip > it ? I tried that, but the "install-grub" procedure refused to function without a device argument. Will probably have to implement an "install-grub-efi" procedure, didn't look much into it yet. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAlkgFPUACgkQoqBt8qM6 VPo9HAf+NnkkGI5Tx6fh9mADSM+uRPlkS6LxoFoXPA1GEz25SYQfxhGJyHRriId+ ZFqiVeCBqbinBZBZVGUhDPVkzZ42Ad8r5WXhADHIhgrPEHFkUflHiZtv152L+0sY 6WKIL5S0U/jXUnmQjguEHlBTlacXdbV7Lmhd3cWuATdXutb0nS5TUy9MKfO0hg0F yGfc1+At2kW5PivGboFhw1TIKUpsnzrEWF9QSGmxxftyflaUZkycIZ8CFmoFpP0S 8ooqBB/6X71AnqLrg6jo7pApbNDZctZx5GSFswkQQ+zR49jgfksJ2nsPeX6NhMnS ARvFK0ZIVWui91ef7a57TBacZ2LFNg== =vQLv -----END PGP SIGNATURE----- --=-=-=--