unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [v2 1/1] doc: Show how to boot result of 'vm-image'.
Date: Tue, 26 Jan 2016 22:11:07 +0100	[thread overview]
Message-ID: <87zivsyrkk.fsf@gnu.org> (raw)
In-Reply-To: <20160126194215.GA19709@jasmine> (Leo Famulari's message of "Tue, 26 Jan 2016 14:42:15 -0500")

Leo Famulari <leo@famulari.name> skribis:

> On Tue, Jan 26, 2016 at 11:08:09AM +0100, Ludovic Courtès wrote:

[...]

>> “Defaults to 128@tie{}MiB, which may be insufficient for some
>> operations.”  (It’s not the daemon specifically, it’s mostly if you want
>> to run X + Xfce, for instance.  The former ‘guix substitute’ used to
>> take quite a lot of memory, but I think that’s no longer the case since
>> we switched to HTTP pipelining.)
>
> I hit this limit while using the "bare-bones" configuration template.
> The system would boot with 128 MiB of RAM but any operations using the
> daemon would fail.

Oh OK.  Well the thing is still using too much memory then (I suspect
it’s ‘guix substitute’ that’s at fault, not the C++ part of the daemon.)

> Also, I looked into how QEMU interprets "megabyte" et al. From the QEMU
> source file "include/qemu-common.h":
> #define M_BYTE     (1ULL << 20)
>
> So, I replaced "megabyte" with "mebibyte" in this paragraph.

Perfect.  :-)

Thanks,
Ludo’.

      reply	other threads:[~2016-01-26 21:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-24 21:22 [v2 0/1] Revised QEMU instructions for manual Leo Famulari
2016-01-24 21:22 ` [v2 1/1] doc: Show how to boot result of 'vm-image' Leo Famulari
2016-01-26 10:08   ` Ludovic Courtès
2016-01-26 19:42     ` Leo Famulari
2016-01-26 21:11       ` 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

  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=87zivsyrkk.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@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).