unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: myglc2 <myglc2@gmail.com>
To: help-guix@gnu.org
Subject: Re: 'guix system vm' questions
Date: Wed, 06 Jul 2016 12:17:29 -0400	[thread overview]
Message-ID: <86eg76rbae.fsf@gmail.com> (raw)
In-Reply-To: CAL1_imn74FwAX2ZMmijOg1oZCG3j24EBeVMOyGTbuui1Gn=COw@mail.gmail.com

David Craven <david@craven.ch> writes:

[...]
>>
>> From: myglc2 <myglc2@gmail.com>
>>
>> David Craven <david@craven.ch> writes:
>>
>>> So I packaged rng-tools and created a shepherd service, but I realized
>>> that the service needs to be started before the activation part of the
>>> lsh service. What's the best way to do this?
>>>
>>> https://git.lysator.liu.se/lsh/lsh/blob/master/src/lsh-make-seed.c#L1075
>>>
>>> On Wed, Jun 29, 2016 at 8:23 PM, David Craven <david@craven.ch> wrote:
>>>> HW_RANDOM_VIRTIO is enabled in the default kernel.
>>>>
>>>> Starting the vm like this enables the hwrng:
>>>> /gnu/store/3rqbwx34kfa789jbywfbxl90nids08cf-run-vm.sh -device virtio-rng-pci
>>>> and it works as can be verified by
>>>> cat /dev/hwrng
>>>>
>>>> The only missing components from what I can tell is packaging rng-tools
>>>> and adding a service to add /dev/hwrng to the entropy pool on boot.
>>>>
>>>> https://git.kernel.org/cgit/utils/kernel/rng-tools/rng-tools.git/
>>>>
>>>>> We should look into QEMU's VirtIO RNG, which could help here:
>>>>> http://wiki.qemu-project.org/Features-Done/VirtIORNG
>>
>> This sounds great. I see you submitted patches. Am I correct in thinking
>> that the next step is to add an lsh-option option that uses rmg-tools
>> instead of lsh-make-seed to set the yarrow seed?
>>
> @myglc2 the simplest workaround to this issue is to add -device
> virtio-rng-pci to your qemu flags ...

Thanks, that works but ...

> ... and patch lsh to use /dev/hwrng in the /bin/lsh-make-seed file I
> linked to in a previous reply.

... I don't follow this. Are you referring to the posts above?

I have your "b58cbf9 * services: Add rngd-service."  patch. Is the idea
to add entropy so we don't need to bang on the keyboard? Or is an
additional patch required/in the pipeline/a self help item?

Thanks - George

  reply	other threads:[~2016-07-06 16:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-03 16:09 'guix system vm' questions David Craven
2016-07-06 16:17 ` myglc2 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-07-07 16:26 David Craven
2016-06-29 18:23 David Craven
2016-06-30 13:10 ` David Craven
2016-07-03 13:53   ` myglc2
2016-06-29  6:57 myglc2
2016-06-29 14:10 ` Thompson, David
2016-06-29 15:48   ` Leo Famulari
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

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=86eg76rbae.fsf@gmail.com \
    --to=myglc2@gmail.com \
    --cc=help-guix@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.
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).