From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: 27605@debbugs.gnu.org
Subject: bug#27605: Lightweight desktop example fails to build with kernel panic
Date: Fri, 07 Jul 2017 15:39:56 +0200 [thread overview]
Message-ID: <87fue874cz.fsf@gnu.org> (raw)
In-Reply-To: <20170707125337.GA11418@jasmine.lan> (Leo Famulari's message of "Fri, 7 Jul 2017 08:53:37 -0400")
Leo Famulari <leo@famulari.name> skribis:
> On Fri, Jul 07, 2017 at 02:23:05PM +0200, Ludovic Courtès wrote:
>> Did you pass --image-size? If not, it could be that the image size
>> estimate is slightly too small (see commit
>> a8ac4f081a9a679498ea42ccfe001f218bba3043).
>>
>> The build log should contain something like:
>>
>> creating ~a image of ~,2f MiB...
>>
>> where ~a is “raw” or “qcow2” depending on the “guix system” command you
>> used.
>>
>> Could you check what happens if you pass a --image-size argument bigger
>> than that?
>
> I doubled it from ~10 GiB to ~20 GiB:
>
>> creating qcow2 image of 19359.59 MiB...
>
> This example template uses EFI, which I'm not that familiar with. But I
> suspect something about the bootloader or filesystems configuration is
> wrong.
>
> From 'gnu/system/examples/lightweight-desktop.tmpl':
>
> ;; Use the UEFI variant of GRUB with the EFI System
> ;; Partition on /dev/sda1.
> (bootloader (grub-configuration (grub grub-efi)
> (device "/dev/sda1")))
Oh right, so the failure is probably unrelated to the image-size
estimate.
Marius, any ideas? :-)
https://bugs.gnu.org/27605
Thanks,
Ludo’.
prev parent reply other threads:[~2017-07-07 13:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-07 3:49 bug#27605: Lightweight desktop example fails to build with kernel panic Leo Famulari
2017-07-07 12:23 ` Ludovic Courtès
2017-07-07 12:53 ` Leo Famulari
2017-07-07 13:21 ` Leo Famulari
2017-07-07 15:16 ` Ludovic Courtès
2017-07-07 16:32 ` Leo Famulari
2017-07-07 17:51 ` Ludovic Courtès
2017-07-07 13:39 ` Ludovic Courtès [this message]
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=87fue874cz.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=27605@debbugs.gnu.org \
--cc=leo@famulari.name \
/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.