From: ludo@gnu.org (Ludovic Courtès)
To: David Craven <david@craven.ch>
Cc: guix-devel <guix-devel@gnu.org>
Subject: ‘guix system vm’ and shared store
Date: Sun, 28 Aug 2016 16:22:21 +0200 [thread overview]
Message-ID: <87eg592cte.fsf_-_@gnu.org> (raw)
In-Reply-To: <CAL1_immvDumz2RjEu=kBPnRpzPVjAj3dRsgqLq+JGCL5Xmrqsg@mail.gmail.com> (David Craven's message of "Sun, 21 Aug 2016 19:38:13 +0200")
Hi,
David Craven <david@craven.ch> skribis:
> So guix doesn't work inside a vm - because /gnu/store is mounted
> readonly.
Right, and also because ‘guix system vm’ creates a VM that shares its
store with the host system.
> 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?
No.
> 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?
Yes, something like that: we need to make /gnu/store a union of the
host’s /gnu/store and a writable tmpfs, and we need to make sure
/var/guix/db/db.sqlite is populated appropriately (images produced by
‘guix system vm-image’ do the latter.)
HTH!
Ludo’.
next prev parent reply other threads:[~2016-08-28 14:22 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 ` Offloading to a VM Ludovic Courtès
2016-08-28 14:38 ` 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 ` Ludovic Courtès [this message]
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=87eg592cte.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).