From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?G=C3=A1bor_Boskovits?= Subject: Re: UEFI testing Date: Wed, 7 Feb 2018 12:09:22 +0100 Message-ID: References: <20180207105805.2e89bbac@scratchpost.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="94eb2c049e5cdf699e05649d538e" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36905) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ejNbR-0008LO-G3 for guix-devel@gnu.org; Wed, 07 Feb 2018 06:09:26 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ejNbQ-0006tW-8u for guix-devel@gnu.org; Wed, 07 Feb 2018 06:09:25 -0500 Received: from mail-it0-x22d.google.com ([2607:f8b0:4001:c0b::22d]:37950) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ejNbQ-0006sR-2X for guix-devel@gnu.org; Wed, 07 Feb 2018 06:09:24 -0500 Received: by mail-it0-x22d.google.com with SMTP id k6so1772478ita.3 for ; Wed, 07 Feb 2018 03:09:24 -0800 (PST) In-Reply-To: <20180207105805.2e89bbac@scratchpost.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Danny Milosavljevic Cc: Guix-devel --94eb2c049e5cdf699e05649d538e Content-Type: text/plain; charset="UTF-8" 2018-02-07 10:58 GMT+01:00 Danny Milosavljevic : > Hi, > > at FOSDEM we've been talking about testing UEFI booting in Guix system > tests. > > The command to use for that is: > > qemu-system-x86_64 -bios $(guix build ovmf)/share/firmware/ovmf_x64.bin > -m 1G -enable-kvm -hda ZZ -serial stdio > > The place where system tests are is gnu/tests/install.scm - it's using > marionette-operating-system to prepare system tests. > > So qemu would have to do a full boot using "-bios". > > There's already an extlinux test there, so it should be easy to use that as > a template (copy %test-installed-extlinux-os to %test-installed-efi-os and > adapt it; also copy the %minimal-extlinux-os definition). > > run-install could gain an option for the bios - which would then be passed > by %test-installed-efi-os . > > I don't have UEFI or a use for it, so this mail is just a heads-up. > > Thanks for looking into this, I guess I will pick it up form here. I've actually dealt with ovmf already in other enviroments. My problem here, is that the ovmf image should be writeable by the vm instance, so that the bootloader nvram variables can be stored. It should be possible to fall back to the uefi backup path though. --94eb2c049e5cdf699e05649d538e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
2018= -02-07 10:58 GMT+01:00 Danny Milosavljevic <dannym@scratchpost.org>:
Hi,

at FOSDEM we've been talking about testing UEFI booting in Guix system = tests.

The command to use for that is:

qemu-system-x86_64 -bios $(guix build ovmf)/share/firmware/ovmf_x64.bi= n -m 1G -enable-kvm -hda ZZ -serial stdio

The place where system tests are is gnu/tests/install.scm - it's using<= br> marionette-operating-system to prepare system tests.

So qemu would have to do a full boot using "-bios".

There's already an extlinux test there, so it should be easy to use tha= t as
a template (copy %test-installed-extlinux-os to %test-installed-efi-os and<= br> adapt it; also copy the %minimal-extlinux-os definition).

run-install could gain an option for the bios - which would then be passed<= br> by %test-installed-efi-os .

I don't have UEFI or a use for it, so this mail is just a heads-up.

Thanks for looking into thi= s, I guess I will pick it up form here.
I've actually dealt with ovmf already in other enviroments.<= /div>
My problem here, is that the o= vmf image should be writeable by the vm instance, so that
the bootloader nvram variables can be stored.= It should be possible to fall back to the uefi backup path though.
=C2=A0

--94eb2c049e5cdf699e05649d538e--