From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ludovic =?UTF-8?Q?Court=C3=A8s?= <ludo@gnu.org>
Subject: bug#35380: disk-image fails to install efi grub
Date: Thu, 02 May 2019 17:16:52 +0200
Message-ID: <875zqsvqcb.fsf@gnu.org>
References: <0935773a-1e21-9576-d569-f97e79ed13dd@s.rendaw.me>
	<87a7gesccy.fsf@gnu.org>
	<323096f6-9382-c3fd-1dc5-486c4737b12f@s.rendaw.me>
	<87d0l2exld.fsf@gnu.org>
	<CAE4v=pgYYFYSwbQt6EdJ-fGD_-yvdxzN7Ooy-NiWB_ScELeKWA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([209.51.188.92]:57965)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1hMDTH-00027h-3A
	for bug-guix@gnu.org; Thu, 02 May 2019 11:18:03 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1hMDTG-00081x-AH
	for bug-guix@gnu.org; Thu, 02 May 2019 11:18:03 -0400
Received: from debbugs.gnu.org ([209.51.188.43]:33170)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
	id 1hMDTG-00080t-65
	for bug-guix@gnu.org; Thu, 02 May 2019 11:18:02 -0400
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1hMDTF-00044L-S3
	for bug-guix@gnu.org; Thu, 02 May 2019 11:18:01 -0400
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.35380.D35380.155681022415567@debbugs.gnu.org>
In-Reply-To: <CAE4v=pgYYFYSwbQt6EdJ-fGD_-yvdxzN7Ooy-NiWB_ScELeKWA@mail.gmail.com>
	("=?UTF-8?Q?G=C3=A1bor?= Boskovits"'s message of "Thu, 2 May 2019
	11:05:00 +0200")
List-Id: Bug reports for GNU Guix <bug-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/bug-guix/>
List-Post: <mailto:bug-guix@gnu.org>
List-Help: <mailto:bug-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=subscribe>
Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org
Sender: "bug-Guix" <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
To: =?UTF-8?Q?G=C3=A1bor?= Boskovits <boskovits@gmail.com>
Cc: 35380-done@debbugs.gnu.org, rendaw <7e9wc56emjakcm@s.rendaw.me>

Hello,

G=C3=A1bor Boskovits <boskovits@gmail.com> skribis:

> I've already looked into that earlier, and supporting this usecase would
> not be
> so hard. We have ovmf after all, and we could stat qemu in efi mode. It
> would not
> be so hard to get the thing in place to do an emergency efi booting setup.
> Why I did not feel comfortable to carry on work in this direction, is that
> we should
> associate a state with the VM-s, namely the file contatining the nvram
> variables of
> the efi firmware. This is needed for full support, but not needed to crea=
te
> a bootable
> system. Wdyt?

I suppose the file that contains variables could be temporary or
read-only in the store?

I=E2=80=99m not familiar with all this.  ISTR that Marius looked into it ba=
ck
then, so perhaps there are ideas to share?

Thanks,
Ludo=E2=80=99.