all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Gábor Boskovits" <boskovits@gmail.com>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: UEFI testing
Date: Wed, 7 Feb 2018 12:09:22 +0100	[thread overview]
Message-ID: <CAE4v=pjP0v8umasXpcyYzxsfVbAOAtAt+8KDk8qj7vOmOHRu5Q@mail.gmail.com> (raw)
In-Reply-To: <20180207105805.2e89bbac@scratchpost.org>

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

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.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.

[-- Attachment #2: Type: text/html, Size: 3122 bytes --]

  reply	other threads:[~2018-02-07 11:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-07  9:58 UEFI testing Danny Milosavljevic
2018-02-07 11:09 ` Gábor Boskovits [this message]
2018-02-08 13:40 ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAE4v=pjP0v8umasXpcyYzxsfVbAOAtAt+8KDk8qj7vOmOHRu5Q@mail.gmail.com' \
    --to=boskovits@gmail.com \
    --cc=dannym@scratchpost.org \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.