From: Leo Famulari <leo@famulari.name>
To: Stefan <stefan-guix@vodafonemail.de>
Cc: 36380@debbugs.gnu.org
Subject: bug#36380: service urandom-seed takes too long on boot
Date: Mon, 28 Dec 2020 21:51:19 -0500 [thread overview]
Message-ID: <X+qZp6UZ9db5yt19@jasmine.lan> (raw)
In-Reply-To: <6A711ED5-B7D9-4276-88C4-08C7ADE2DFC0@vodafonemail.de>
On Mon, Dec 28, 2020 at 12:28:09AM +0100, Stefan wrote:
> “-object rng-random,id=id,filename=/dev/random
> Creates a random number generator backend which obtains entropy from a device on the host. The id parameter is a unique ID that will be used to reference this entropy backend from the virtio-rng device. The filename parameter specifies which file to obtain entropy from and if omitted defaults to /dev/urandom.”
I see, so there is the problem.
It should either be changed to "filename=/dev/urandom", or the QEMU
rng-random mechanism should be disabled.
We still need to implement a timeout to workaround this kind of
misconfiguration... help wanted :)
next prev parent reply other threads:[~2020-12-29 2:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 18:12 bug#36380: service urandom-seed takes too long on boot Robert Vollmert
2019-06-26 9:41 ` Alex Sassmannshausen
2019-06-26 15:47 ` Leo Famulari
2019-06-26 16:02 ` Robert Vollmert
2019-06-27 19:19 ` Leo Famulari
2019-06-27 15:20 ` Ludovic Courtès
2019-06-27 19:03 ` Leo Famulari
2019-06-27 20:00 ` Ludovic Courtès
2019-06-28 6:47 ` Robert Vollmert
2019-06-28 17:24 ` Leo Famulari
2019-07-11 17:44 ` Leo Famulari
2019-07-11 21:33 ` Ludovic Courtès
2019-07-17 21:04 ` bug#36380: related article (Debian) Robert Vollmert
2020-03-22 8:43 ` bug#36380: service urandom-seed takes too long on boot Brice Waegeneire
2020-03-22 20:19 ` Leo Famulari
2020-12-27 15:00 ` Stefan
2020-12-27 23:09 ` Leo Famulari
2020-12-27 23:28 ` Stefan
2020-12-29 2:51 ` Leo Famulari [this message]
2021-02-07 15:23 ` raid5atemyhomework via Bug reports for GNU Guix
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=X+qZp6UZ9db5yt19@jasmine.lan \
--to=leo@famulari.name \
--cc=36380@debbugs.gnu.org \
--cc=stefan-guix@vodafonemail.de \
/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).