unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: x@wilsonb.com
To: help-guix@gnu.org, bw@inskydata.com
Subject: Re: *** GUIX SYSTEM DISK-IMAGE HANGS PINEBOOK PRO ***
Date: Thu, 14 Nov 2019 09:19:51 +0900	[thread overview]
Message-ID: <5dcc9da7.GBz7tmLyx5yXhMfc%x@wilsonb.com> (raw)
In-Reply-To: <E876FF8E-E1E6-4A6B-A15E-12C431F22633@inskydata.com>

I had a similar issue building a disk-image. It was on an x86 machine, and the
build would error out right at that point. The fix was to put add my user to
the 'kvm' group.

From looking at top during the build, it seems that the disk-image derivation
is doing something with qemu. Is there even ARM support in the KVM? I am
illiterate on that kind of thing, but hopefully this gives you a lead.

Brian Woodcox <bw@inskydata.com> wrote:

> I am using a Pinebook Pro (aarch64) to build a disk image.  However the build process stops very quickly when it gets to the ...-disk-image.drv...
>
> The guix --version is guix (GNU Guix) d673993...1ce0f20 
>
> The command that I am issuing is:
>
> guix system disk-image -e "(@ (gnu system install) rockpro64-installation-os)"
>
> I did not add --system=aarch64-linux as that should be implicit, since I am running this on an aarch64 system.
>
> Also target-arm32 is required, so I had to edit the guix/utils.scm file so that would be set as true as follows (this is just an ugly hack):
>
> (define (target-arm32?)
>   (string-prefix? "aarch" (or (%current-target-system) (%current-system))))
>
> Using strace on the command does not yield any obvious error.
>
> building /gnu/store/qhc1l9kl9ly864r7vzpwfkql3fwa1dmp-system.drv...
> building /gnu/store/587bzj89p3xrylishwvv3qcgmz9qliym-shepherd.conf.drv...
> building /gnu/store/3wn68s1vs4l11jxs68k35dbzhi89ixb9-gc-roots.drv...
> building /gnu/store/q1fidshxfja4a3np3mzwz9c3bih0s722-boot.drv...
> building /gnu/store/7qn53w2sdrh2vfaykaaklgzv4qh68xqx-system.drv...
> building /gnu/store/i6b2h9l9mv2ckdgcqmszwg647x9v3jlh-extlinux.conf.drv...
> building /gnu/store/v7nhck2b7i9djf0fnk61lvgl3p4ff2gy-builder-in-linux-vm.drv...
> building /gnu/store/jfqr107g0icghv07y3fii0i8afddbj9j-linux-vm-loader.drv...
> building /gnu/store/wvk6gkbn3894dfwbb0y7nnnzrhljp3i0-disk-image.drv...
> \ ^C
>
> If anyone knows what the issue is, or how I could debug it, I would be happy to hear it.
>
> Thanks.
>
> Brian.
>

  reply	other threads:[~2019-11-14  0:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-13 22:57 *** GUIX SYSTEM DISK-IMAGE HANGS PINEBOOK PRO *** Brian Woodcox
2019-11-14  0:19 ` x [this message]
2019-11-14  4:49   ` Brian Woodcox
2019-11-14  9:13 ` Efraim Flashner

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=5dcc9da7.GBz7tmLyx5yXhMfc%x@wilsonb.com \
    --to=x@wilsonb.com \
    --cc=bw@inskydata.com \
    --cc=help-guix@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.
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).