<mark_weaver>the code to build these images is in guix/gnu/system/vm.scm. search there for /dev/vda.
<mark_weaver>it might be easier to just build a new image. 'system-qemu-image' accepts an optional keyword argument for the disk image size. It defaults to 900 MiB.
<mark_weaver>to build the image with the defaults: ./pre-inst-env guix build -e '(@ (gnu system vm) system-qemu-image)'
<mark_weaver>it's a bit awkward, but to make a larger image, it would be something like: ./pre-inst-env guix build -e '(@ (gnu system vm) system-qemu-image (@@ (gnu system vm) %demo-operating-system) (* 1.5 (expt 2 30)))'
<mark_weaver>strange. the build directory for glib-2.38.0 was left in /tmp, but looking at the build log, it looks like it completed successfully, and the output is in /nix/store/*-glib-2.38.0 (with the same hash as in the build log)
<mark_weaver>this is on the Loongson 3A machine, which I periodically run tests on where I do "guix build -K $pkg" for almost every $pkg listed by "guix package -A ."
<sbp>civodul: hey, had a few notes on my guix install the other day:
<sbp>1. there was a permissions error writing to $GUIX/nix/profiles/per-user/sbp *after* a long installation process. the permissions of this directory should have been checked at the very start of the process
<sbp>2. since $GUIX/nix/profiles/per-user belongs to root, root has to manually add and chown a new directory for every user. can't users manage their own profiles themselves? why does ~/.guix-profile *have* to be a symlink?
<sbp>3. there was an "guix package: error: build failed: unexpected end-of-file" error when trying to install python. it was transient: when I tried installing again straight away, it worked without that error
<sbp>4. package download statuses keep getting printed over and over. a_e noted that this is because my term was too narrow, but I use the standard 80 columns. progress indicators with CR should be robust
<sbp>5. after another long installation process, I got "error: build failed: builder does not have write permission to `/nix/store'; try `chgrp 1001 /nix/store; chmod 1775 /nix/store'". this should also have been checked at the *start* of the installation process
<civodul>actually, downloading goes through that 'startBuilder' method, which does the permission check
<civodul>so i wonder how it failed to be detected earlier
<sbp>hmm. when I started it again (after fixing the permissions error), it started with xz. the next one was bzip2. so it was downloading packages in a different order to the previous invocation, including one that it had already downloaded
<sbp>(was followed by gawk, perl, etc., and eventually python)
<gzg>civodul: I've played around with it on my Debian install, that had xorg already setup and I just added it to said .xinintrc -- right now I'm on my minimal Parabola install, I dedicated to Guix and tryieg to figure it out.
<gzg>Eventually, I want to generate and possibly host a test VM with GNU ~0.5+ Emacs, and Guile-WM.