From: Leo Famulari <leo@famulari.name>
To: Jan Nieuwenhuizen <janneke@gnu.org>
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 17:48:20 -0400 [thread overview]
Message-ID: <20170619214820.GA2317@jasmine.lan> (raw)
In-Reply-To: <87vanrc16w.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 942 bytes --]
On Mon, Jun 19, 2017 at 07:55:03PM +0200, Jan Nieuwenhuizen wrote:
> 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)?
I chose 2GiB for those images because it's pretty easy to grow a
partition and ext4 filesystem from a running system. On the other hand,
I couldn't find an easy way to shrink them.
We can't predict the size of the virtual block device storage provided
by a VPS hoster, so I chose this small size with these expectations:
1) 2GiB will never be too big
2) users will resize after booting
I didn't come up with a better solution for the problem of not knowing
the storage size in advance. What do you think?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-06-19 21:49 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
2017-06-19 21:48 ` Leo Famulari [this message]
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=20170619214820.GA2317@jasmine.lan \
--to=leo@famulari.name \
--cc=27401@debbugs.gnu.org \
--cc=janneke@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).