From: Leo Famulari <leo@famulari.name>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 27684@debbugs.gnu.org
Subject: bug#27684: Can't build disk-images or vm-images on core-updates
Date: Fri, 14 Jul 2017 11:13:22 -0400 [thread overview]
Message-ID: <20170714151322.GB5467@jasmine.lan> (raw)
In-Reply-To: <20170714161457.72ddd51b@scratchpost.org>
[-- Attachment #1: Type: text/plain, Size: 978 bytes --]
On Fri, Jul 14, 2017 at 04:14:57PM +0200, Danny Milosavljevic wrote:
> Hi Leo,
>
> On Thu, 13 Jul 2017 17:57:21 -0400
> Leo Famulari <leo@famulari.name> wrote:
>
> > Both `guix system disk-image` and `guix system vm-image` fail for me on
> > core-updates. Read-only VMs seem to work fine. I'm currently checking to
> > see if it fails when building on GuixSD.
> >
> > I'm using x86_64-linux on a foreign distro with Linux 4.12.1. The host
> > filesystem is ext4. I'm building a kernel on GuixSD so I can test it
> > there.
> >
> > I changed the value of 'memory-size' to 4096 (4 GB) in (gnu build vm)
> > for some of my tests, but the problem persists. I also tried using QEMU
> > without any of the bug-fix patches, but no joy.
>
> Does the system image work when you run it on the bare metal (without qemu or anything)?
Which system image? I can use the 0.13.0 release disk-image without any
trouble, but I can't create new ones from core-updates.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-07-14 15:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 21:57 bug#27684: Can't build disk-images or vm-images on core-updates Leo Famulari
2017-07-13 22:05 ` Leo Famulari
2017-07-14 14:14 ` Danny Milosavljevic
2017-07-14 15:13 ` Leo Famulari [this message]
2017-07-17 14:02 ` Ludovic Courtès
2017-07-17 20:56 ` Leo Famulari
2017-07-18 13:57 ` Ludovic Courtès
2017-07-18 18:56 ` Leo Famulari
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=20170714151322.GB5467@jasmine.lan \
--to=leo@famulari.name \
--cc=27684@debbugs.gnu.org \
--cc=dannym@scratchpost.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).