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: [PATCH 1/1] doc: Show how to boot result of 'vm-image'.
Date: Sun, 24 Jan 2016 16:02:47 -0500	[thread overview]
Message-ID: <20160124210247.GA28700@jasmine> (raw)
In-Reply-To: <87io2iopbq.fsf@gnu.org>

On Sun, Jan 24, 2016 at 06:32:57PM +0100, Ludovic Courtès wrote:
> Leo Famulari <leo@famulari.name> skribis:
> 
> > * doc/guix.texi (Invoking guix system): Explain how to boot the QEMU
> > images created by vm-image.
> 

[...]

> I’m thinking there are often questions about using GuixSD in a VM etc.,
> so it may well deserve one or two sections of its own.
> 
> What about leaving the above sentence here, and appending:
> 
>   @xref{Running GuixSD in a VM}, for more information on how to run the
>   image in a virtual machine.
> 
> ?
> 
> The rest of the material you added would then go to the new “Running
> GuixSD in a VM” section, which could go maybe right after “Invoking guix
> system”.  WDYT?

That sounds good, done!

> 
> > +When using @code{vm-image}, the returned image is in qcow2 format, which
> > +the QEMU emulator can efficiently use.
> 
> In the new section, this would need to be slightly adjusted to give more
> context, like:
> 
>   One way to run GuixSD in a virtual machine is to build a GuixSD
>   virtual machine image using @command{guix system vm-image}
>   (@pxref{Invoking guix system}).  The returned image is in qcow2
>   format, which the @uref{http://qemu.org/, QEMU emulator} can
>   efficiently use.

Thanks for this :)

[...]

> > +@example
> > +$ qemu-system-x86_64 \
> > +-net user \
> > +-net nic,model=virtio \
> > +-enable-kvm \
> > +-m 256 \
> > +/tmp/qemu-image
> > +@end example
> 
> I think it would be nicer to put it on 3 lines.

Done.

[...]

> I would typeset it as:
> 
>   @table @code
>   @item qemu-system-x86_64
>   This specifies the hardware platform to…
> 
>   @item -net user
>   Enable unpriviliged user-mode networking…
>   …
> 
>   @end @table
> 
> With all this, it’s going to look perfect!  :-)

Thank you for this example. I really need to study what Texinfo can do.

> 
> Another question that people often ask is how to install GuixSD from the
> installation image in a VM.  Maybe that could be added eventually in a
> subsection of this new node?

I agree, that would be useful. If anybody knows how to do that, they
should chime in.

> 
> Thank you!

Thanks for your helpful feedback!

> 
> Ludo’.

      reply	other threads:[~2016-01-24 21:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-15 10:12 [PATCH 0/1] Show to use vm-image Leo Famulari
2016-01-15 10:12 ` [PATCH 1/1] doc: Show how to boot result of 'vm-image' Leo Famulari
2016-01-23 20:45   ` Leo Famulari
2016-01-24 17:32   ` Ludovic Courtès
2016-01-24 21:02     ` Leo Famulari [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=20160124210247.GA28700@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).