From: Jan Nieuwenhuizen <janneke@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: 27401@debbugs.gnu.org
Subject: [bug#27401] [PATCH] doc: Suggest a QEMU image size large enough for the system examples.
Date: Mon, 19 Jun 2017 19:55:03 +0200 [thread overview]
Message-ID: <87vanrc16w.fsf@gnu.org> (raw)
In-Reply-To: <4fedabaa491c5a46b8d437748f9071a4aa1d966d.1497676494.git.leo@famulari.name> (Leo Famulari's message of "Sat, 17 Jun 2017 01:14:54 -0400")
Leo Famulari writes:
> * doc/guix.texi (Installing GuixSD in a Virtual Machine): Increase suggested
> image size from 5 GB to 50 GB.
LGTM, however -- What about something like this patch too? I seems that
the VMs we create (although they are of the ballooning cow2 kind), are
2GiB -- i.e., almost unusable for Real Stuff (TM)?
$ git diff
diff --git a/Makefile.am b/Makefile.am
index a3b3e557a..ff2ae120b 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -592,7 +592,7 @@ GUIXSD_VM_IMAGE_BASE = guixsd-vm-image-$(PACKAGE_VERSION)
GUIXSD_INSTALLATION_IMAGE_SIZE ?= 950MiB
# Size of the VM image (for x86_64 typically).
-GUIXSD_VM_IMAGE_SIZE ?= 2GiB
+GUIXSD_VM_IMAGE_SIZE ?= 50GiB
# The release process works in several phases:
#
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
next prev parent reply other threads:[~2017-06-19 17:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-17 5:14 [bug#27401] [PATCH] doc: Suggest a QEMU image size large enough for the system examples Leo Famulari
2017-06-17 12:20 ` Marius Bakke
2017-06-19 17:55 ` Jan Nieuwenhuizen [this message]
2017-06-19 21:48 ` Leo Famulari
2017-06-20 18:03 ` Jan Nieuwenhuizen
2017-06-23 21:13 ` Leo Famulari
2017-06-26 11:51 ` [bug#27401] Guessing the disk image size in 'guix system' Ludovic Courtès
2017-06-29 22:30 ` 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=87vanrc16w.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=27401@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).