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

On Tue, Jan 26, 2016 at 11:08:09AM +0100, Ludovic Courtès wrote:
> Leo Famulari <leo@famulari.name> skribis:
> 
> > * doc/guix.texi (Running GuixSD in a VM): New node.
> > (Invoking guix system): Add reference to 'Running GuixSD in a VM'.
> 
> [...]
> 
> > +@node Running GuixSD in a VM
> > +@subsection Running GuixSD in a VM
> 
> s/VM/virtual machine/ on the second line.
> 
> > +One way to run GuixSD in a virtual machine is to build a GuixSD virtual
> 
> After “virtual machine”, add “(VM)” to introduce the acronym.
> 
> > +machine image using @command{guix system vm-image} (@pxref{Invoking guix
> > +system}). The returned image is in qcow2 format, which the
>            ^^
> Please make sure that all the end-of-sentence periods are followed by
> two spaces or a newline (info "(texinfo) Not Ending a Sentence").
> 
> > +$ qemu-system-x86_64 \
> > +-net user -net nic,model=virtio \
> > +-enable-kvm -m 256 /tmp/qemu-image
> 
> Would be nice to align the 2nd and 3rd line below the ‘e’ of ‘qemu’.
> 
> > +And the annotated version:
> 
> Maybe “Here is what each of these options means:”.
> 
> > +x86_64, you can get a list of available NIC models by running
> > +`qemu-system-x86_64 -net nic,model=help`.
> 
> Instead of backquotes, use @command{…}.
> 
> > +@item -enable-kvm
> > +If your system has hardware virtualization extensions, enabling the
> > +kernel virtual machine will make things run faster.
> 
> s/kernel virtual machine/Linux kernel's virtual machine support (KVM)/
> 
> > +@item -m 256
> > +RAM available to the guest OS, in megabytes. Defaults to 128 megabytes,
> > +which is not enough for the Guix daemon.
> 
> “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.

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.

> 
> > +@item /tmp/qemu-image
> > +The filesystem path of the qcow2 image.
> 
> s/filesystem path/file name/
> 
> OK with these changes, thanks a lot!

Thanks for your help!

> 
> Ludo’.

  reply	other threads:[~2016-01-26 19:42 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 [this message]
2016-01-26 21:11       ` 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=20160126194215.GA19709@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@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 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).