all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 27605-done@debbugs.gnu.org
Subject: bug#27605: Lightweight desktop example fails to build with kernel panic
Date: Fri, 7 Jul 2017 09:21:51 -0400	[thread overview]
Message-ID: <20170707132151.GA16788@jasmine.lan> (raw)
In-Reply-To: <20170707125337.GA11418@jasmine.lan>

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

On Fri, Jul 07, 2017 at 08:53:37AM -0400, Leo Famulari wrote:
> 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.

Actually, false alarm! After increasing the image size to 20 GiB, I
missed the messages about being out of space. Sorry for the noise!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-07-07 13:22 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 [this message]
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

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=20170707132151.GA16788@jasmine.lan \
    --to=leo@famulari.name \
    --cc=27605-done@debbugs.gnu.org \
    --cc=ludo@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.