From: "Ludovic Courtès" <ludo@gnu.org>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 50676@debbugs.gnu.org
Subject: bug#50676: [core-updates-frozen] Image production is broken.
Date: Mon, 20 Sep 2021 00:37:37 +0200 [thread overview]
Message-ID: <87v92wqjim.fsf@gnu.org> (raw)
In-Reply-To: <87fsu07gay.fsf@gnu.org> (Mathieu Othacehe's message of "Sun, 19 Sep 2021 15:09:41 +0000")
Hi,
Mathieu Othacehe <othacehe@gnu.org> skribis:
> When a producing a disk-image, the system derivations are built twice:
What command did you use?
I tried:
./pre-inst-env guix system image -t qcow2 gnu/system/examples/bare-bones.tmpl
Running:
qemu-system-x86_64 -m 1024 -enable-kvm -snapshot /gnu/store/…-image.qcow2
drops me in the GRUB rescue shell right from the start, but I think
that’s because the command surprisingly builds an EFI image, as can be
seen from the generated genimage.cfg:
--8<---------------cut here---------------start------------->8---
image image {
hdimage {}
partition GNU-ESP {
partition-type = 0xEF
image = "/gnu/store/zfia31ypdlcx5d7sxhwmh4d8jsq33cqb-partition.img"
offset = "1048576"
}
partition Guix_image {
partition-type = 0x83
image = "/gnu/store/8v4m9cqrgvmp3akajv2pk1pvcdrswx2g-partition.img"
offset = "0"
}
}
--8<---------------cut here---------------end--------------->8---
> The installed Grub configuration file in /boot/grub/grub.cfg points to a
> system that is *not* part of the closure. The second Grub configuration
> file shown above points to the other system that *is* part of the
> closure.
>
> While booting the image in QEMU, the boot fails when trying to access
> the missing /gnu/system/xxx-system/boot file.
Uh.
Ludo’.
next prev parent reply other threads:[~2021-09-19 22:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-19 15:09 bug#50676: [core-updates-frozen] Image production is broken Mathieu Othacehe
2021-09-19 22:37 ` Ludovic Courtès [this message]
2021-09-20 8:57 ` Mathieu Othacehe
2021-09-20 12:52 ` Mathieu Othacehe
2021-09-22 10:37 ` Ludovic Courtès
2021-09-24 22:55 ` Ludovic Courtès
2021-09-26 19:40 ` Mathieu Othacehe
2021-09-27 15:57 ` 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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v92wqjim.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=50676@debbugs.gnu.org \
--cc=othacehe@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).