From: Leo Famulari <leo@famulari.name>
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: myglc2 <myglc2@gmail.com>, help-guix <help-guix@gnu.org>
Subject: Re: 'guix system vm' questions
Date: Wed, 29 Jun 2016 11:48:42 -0400 [thread overview]
Message-ID: <20160629154842.GA26047@jasmine> (raw)
In-Reply-To: <CAJ=Rwfbj4oAxpqm0VgzBdW33E_9tCtFQNW+VPO1fUWT4z6DMpw@mail.gmail.com>
On Wed, Jun 29, 2016 at 10:10:35AM -0400, Thompson, David wrote:
> On Wed, Jun 29, 2016 at 2:57 AM, myglc2 <myglc2@gmail.com> wrote:
> > I have a headless server running Guix/Debian 8.3 on which I would like
> > to run some guix vms. So far, I have a script (see mkvm.sh, attached)
> > that runs a single vm. It has some issues:
> >
> > 1) lsh-service hangs waiting for keystrokes on the QEMU console
>
> LSH needs to be initialized with a key on first boot, which is why you
> need to type to create entropy. This sucks for automation, so I would
> recommend OpenSSH instead, but we don't have an openssh-service yet.
In your operating system configuration, you can pass 'initialize? #f' to
lsh-service to skip the SSH seed and host-key initialization. You will
need to initialize the LSH service later, before you can use it.
How does OpenSSH get entropy without blocking on first boot? Before
shipping an openssh-service, we should make sure that OpenSSH doesn't
assume that /dev/urandom is safe to use; my understanding is that it
isn't safe immediately after first boot.
We should look into QEMU's VirtIO RNG, which could help here:
http://wiki.qemu-project.org/Features-Done/VirtIORNG
next prev parent reply other threads:[~2016-06-29 15:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 6:57 'guix system vm' questions myglc2
2016-06-29 14:10 ` Thompson, David
2016-06-29 15:48 ` Leo Famulari [this message]
2016-07-01 20:15 ` myglc2
2016-07-02 13:06 ` Ludovic Courtès
2016-07-03 13:47 ` myglc2
2016-07-11 19:32 ` Leo Famulari
2016-06-30 21:20 ` myglc2
-- strict thread matches above, loose matches on Subject: below --
2016-06-29 18:23 David Craven
2016-06-30 13:10 ` David Craven
2016-07-03 13:53 ` myglc2
2016-07-03 16:09 David Craven
2016-07-06 16:17 ` myglc2
2016-07-07 16:26 David Craven
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=20160629154842.GA26047@jasmine \
--to=leo@famulari.name \
--cc=dthompson2@worcester.edu \
--cc=help-guix@gnu.org \
--cc=myglc2@gmail.com \
/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).