all messages for Guix-related lists mirrored at yhetil.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: qemu instructions for manual
Date: Tue, 12 Jan 2016 22:50:33 +0100	[thread overview]
Message-ID: <871t9ma2mu.fsf@gnu.org> (raw)
In-Reply-To: <20160111200317.GA8686@jasmine> (Leo Famulari's message of "Mon, 11 Jan 2016 15:03:17 -0500")

Leo Famulari <leo@famulari.name> skribis:

> This appears to be the minimum QEMU invocation that works:
> $ qemu-system-x86_64 \
> -net user \
> -net nic,model=virtio \
> -m 256 \
> ./qemu-image

In practice -enable-kvm is highly recommended too.  I think anything
less than 5 to 8(?) years old supports virtualization extensions.

> Annotated version:
> # System type to emulate. Does this have to match the host hardware? Can
> # "foreign" arch machine images be built with Guix?
> $ qemu-system-x86_64 \

In theory we should be able to cross-compile complete GuixSD images to
other architectures, but that’s never been tried and there are probably
lots of build issues on the way, so let’s say that this has to match the
hardware platform or a sibling thereof (e.g., i686 code can be built on
x86_64.)

> # Unprivileged user mode networking. Guest can access host but not vice versa.
> # If you don't choose a network stack, the boot process will fail.
> -net user \
>
> # You must create a network interface of a given model. You can get a list of
> # available NIC types by running `qemu-system-$arch -net nic,model=help`. If
> # you don't create a NIC, the boot process will fail.
> -net nic,model=virtio \
>
> # RAM available to the guest OS. Defaults to 128 megabytes, which is not enough
> # for the Guix daemon. More is better.
> -m 256 \
>
> OPTIONAL: If your system is x86 with hardware virtualization extensions,
> enabling the kernel virtual machine will make things go much faster.
> -enable-kvm \
>
> # Path to the virtual machine image
> ./qemu-image

Sounds good!

Note that our QEMU package installs two Info manuals.  They are sparse,
but helpful.

In the Guix manual, and interesting thing would be an “Installating
GuixSD in a VM” section.  This is a bit more involved than the above,
because you need a target disk image separate from the installation
image, but the above is a good start.

Thanks,
Ludo’.

      reply	other threads:[~2016-01-12 21:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-11 20:03 qemu instructions for manual Leo Famulari
2016-01-12 21:50 ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871t9ma2mu.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 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.