unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: David Craven <david@craven.ch>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Offloading to a VM
Date: Sun, 28 Aug 2016 16:30:52 +0200	[thread overview]
Message-ID: <877fb12cf7.fsf_-_@gnu.org> (raw)
In-Reply-To: <CAL1_im=9YuCk0CvnWqAvnmGjs+qUndLqznXn5kgrfdib5yj4cQ@mail.gmail.com> (David Craven's message of "Sat, 27 Aug 2016 12:31:18 +0200")

Hello!

David Craven <david@craven.ch> skribis:

> On Sun, Aug 21, 2016 at 7:38 PM, David Craven <david@craven.ch> wrote:
>> So guix doesn't work inside a vm - because /gnu/store is mounted
>> readonly. To be able to offload arm builds once guix system vm
>> --system=armhf-linux works, /gnu/store needs to be writeable.
>>
>> Can multiple daemons concurrently use the same store?
>>
>> or alternatively, can we move the
>>
>> (unless (zero? (system* unionfs "-o"
>>
>> "cow,allow_other,use_ino,suid,dev,max_files=65536"
>>                                 "/rw-root=RW:/real-root=RO"
>>                                 "/root"))
>>           (error "unionfs failed"))
>>
>> to after the 9p filesystems have been mounted, so that the unionfs
>> allows writing to /gnu/store too?
>
> I'd appreciate some ideas on how to best tackle this problem
> (offloading builds to a guix system vm instance) =)

Ooh, since I’m reading messages in the wrong order, I missed the
original intent.

If you want to offload to VMs of a different system type, you could of
course have a full blown VM with an SSH daemon running, and have the
main machine offload to that one (the VM would need to have its own
store and its own disk, though.)

However, a more efficient way to do that would be to use the “build
hook” mechanism of the daemon (this is how ‘guix offload’ gets invoked
by guix-daemon.)  That way, a full VM would not be needed; in fact, we
could probably use QEMU’s ability to run ELF programs directly:

--8<---------------cut here---------------start------------->8---
$ qemu-arm $(guix build coreutils -s armhf-linux |grep -v debug)/bin/uname -a
Linux pluto 4.7.0-gnu #1 SMP 1 armv7l GNU/Linux
$ uname -a
Linux pluto 4.7.0-gnu #1 SMP 1 x86_64 GNU/Linux
--8<---------------cut here---------------end--------------->8---

The idea was briefly discussed at
<http://debbugs.gnu.org/cgi/bugreport.cgi?bug=20239>.

  reply	other threads:[~2016-08-28 14:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-19  7:50 Build machine sysadmin support Ludovic Courtès
2016-08-21 12:42 ` David Craven
2016-08-21 14:34   ` David Craven
2016-08-21 17:38     ` David Craven
2016-08-27 10:31       ` David Craven
2016-08-28 14:30         ` Ludovic Courtès [this message]
2016-08-28 14:38           ` Offloading to a VM David Craven
2016-08-29 12:54             ` Ludovic Courtès
2016-08-29 12:56               ` David Craven
2016-09-03 14:27                 ` David Craven
2016-09-03 14:32                   ` David Craven
2016-09-05 20:30                     ` Ludovic Courtès
2016-09-05 20:50                       ` David Craven
2016-09-05 20:28                   ` Ludovic Courtès
2016-08-28 14:22       ` ‘guix system vm’ and shared store Ludovic Courtès
2016-08-28 14:33   ` Build machine sysadmin support 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=877fb12cf7.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --cc=david@craven.ch \
    --cc=guix-devel@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).