From: "Ludovic Courtès" <ludo@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: Damien Cassou <damien@cassou.me>, 39815@debbugs.gnu.org
Subject: bug#39815: Sharing the store between a host and a guest
Date: Sun, 08 Mar 2020 23:16:17 +0100 [thread overview]
Message-ID: <87d09m7ary.fsf@gnu.org> (raw)
In-Reply-To: <20200228210753.GA30122@jasmine.lan> (Leo Famulari's message of "Fri, 28 Feb 2020 16:07:53 -0500")
Hi!
Leo Famulari <leo@famulari.name> skribis:
> As you found, what you get with `guix system vm` is read-only. Even
> though you copied build-vm.sh out of /gnu/store, it is just a shell
> script that refers to immutable data in the host /gnu/store.
>
> In order to share the store with a VM, you would need to also share the
> store database — at least /var/guix/db if not all of /var/guix — and
> also use the host's guix-daemon.
>
> It would be great to support your use case but I don't think anyone has
> worked on it yet.
Unfortunately, the Unix-domain socket in /var/guix/daemon-socket cannot
be shared over 9p AFAICS (with ‘guix system vm --expose’).
However, one thing that could work is to:
1. in the guest, set GUIX_DAEMON_SOCKET=guix://localhost:1234;
2. set up QEMU port forwarding such that the guest’s port 1234 is
somehow redirected to a port the host guix-daemon listens to (with
‘--listen’);
3. share /var/guix with the guest.
It would be easier if Unix-domain sockets could be forwarded between the
host and the guest, but that doesn’t seem to be the case. :-/
Ludo’.
next prev parent reply other threads:[~2020-03-08 22:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 20:28 bug#39815: Sharing the store between a host and a guest Damien Cassou
2020-02-27 20:33 ` raingloom
2020-02-28 6:50 ` Damien Cassou
2020-02-28 21:07 ` Leo Famulari
2020-02-29 14:11 ` Damien Cassou
2020-03-08 22:16 ` Ludovic Courtès [this message]
2020-03-09 13:00 ` Damien Cassou
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d09m7ary.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=39815@debbugs.gnu.org \
--cc=damien@cassou.me \
--cc=leo@famulari.name \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.