From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: 27684@debbugs.gnu.org
Subject: bug#27684: Can't build disk-images or vm-images on core-updates
Date: Tue, 18 Jul 2017 15:57:46 +0200 [thread overview]
Message-ID: <87wp75x2xx.fsf@gnu.org> (raw)
In-Reply-To: <20170717205619.GA2568@jasmine.lan> (Leo Famulari's message of "Mon, 17 Jul 2017 16:56:19 -0400")
Leo Famulari <leo@famulari.name> skribis:
> On Mon, Jul 17, 2017 at 04:02:14PM +0200, Ludovic Courtès wrote:
>> The log shows that building the disk-image derivation starts with:
>>
>> --8<---------------cut here---------------start------------->8---
>> creating raw image of 102400.00 MiB...
>> Formatting '/gnu/store/yv5r65584aaml86hc0xrgyffnp70ri36-disk-image', fmt=raw size=107374182400
>> --8<---------------cut here---------------end--------------->8---
>>
>> That’s a lot, no?
>
> Yes, I specified it manually while debugging.
>
>> Regardless, memory consumption in the VM is not supposed to be
>> proportional to the size of the image being created.
>
> Indeed, the problem exists also when I don't pick a size manually.
>
>> The allocation failure happens while copying files:
>
> [...]
>
>> Does that work on previous master with Linux-libre 4.12.0 (current
>> master is at 4.12.2)? (This would allow us to determine if this is an
>> ext4 bug, who knows…)
>
> Yes, I tested with a variety of kernels and on the master branch as
> well.
>
>> If it does, then the only other issue I can think of is if Guile itself,
>> while running ‘copy-recursively’ from (guix build utils), eats memory
>> proportional to the number of files, leading to an OOM condition.
>> However the kernel message don’t report it as an OOM, AFAICS.
>
> I'm wondering if it's related to the Guile 2.0 / 2.2 mismatch in the
> initrd, discussed previously:
>
> https://lists.gnu.org/archive/html/guix-devel/2017-07/msg00220.html
>
> Guile 2.0 would need to rebuild all the 2.2 modules it finds.
This works for me now:
--8<---------------cut here---------------start------------->8---
$ ./pre-inst-env guix system disk-image gnu/system/install.scm
*** output flushed ***
$ file /gnu/store/37ppm08ggdds3i06h4la0wdzilcnladm-disk-image
/gnu/store/37ppm08ggdds3i06h4la0wdzilcnladm-disk-image: DOS/MBR boot sector
$ git describe
v0.13.0-1474-gef03d8dc3
--8<---------------cut here---------------end--------------->8---
Could you check if it works for you?
It’s a much smaller image than what you tried (1G vs. 102G).
Ludo’.
next prev parent reply other threads:[~2017-07-18 13:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 21:57 bug#27684: Can't build disk-images or vm-images on core-updates Leo Famulari
2017-07-13 22:05 ` Leo Famulari
2017-07-14 14:14 ` Danny Milosavljevic
2017-07-14 15:13 ` Leo Famulari
2017-07-17 14:02 ` Ludovic Courtès
2017-07-17 20:56 ` Leo Famulari
2017-07-18 13:57 ` Ludovic Courtès [this message]
2017-07-18 18:56 ` Leo Famulari
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=87wp75x2xx.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=27684@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 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).