~ruther/guix-local

98a8b48a69b8208475c9a1e40d09517f8643b8cb — Ludovic Courtès 3 years ago fe149b0
doc: Suggest more RAM for "Running Guix in a VM".

Fixes <https://issues.guix.gnu.org/57474>.
Reported by Michael F. Lamb <mike@orbital.rodeo>.

Running 'guix pull' to target current revisions would lead to memory
exhaustion.  Bumping the memory size works around that.

* doc/guix.texi (Running Guix in a VM): Change "-m 1024" to "-m 2048".
1 files changed, 2 insertions(+), 2 deletions(-)

M doc/guix.texi
M doc/guix.texi => doc/guix.texi +2 -2
@@ 38494,7 38494,7 @@ image -t qcow2} on x86_64 hardware:
@example
$ qemu-system-x86_64 \
   -nic user,model=virtio-net-pci \
   -enable-kvm -m 1024 \
   -enable-kvm -m 2048 \
   -device virtio-blk,drive=myhd \
   -drive if=none,file=/tmp/qemu-image,id=myhd
@end example


@@ 38521,7 38521,7 @@ virtual machine support (KVM) of the Linux kernel will make things run
faster.

@c To run Xfce + 'guix pull', we need at least 1G of RAM.
@item -m 1024
@item -m 2048
RAM available to the guest OS, in mebibytes.  Defaults to 128@tie{}MiB,
which may be insufficient for some operations.