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: Sun, 27 Dec 2020 18:09:56 -0500 [thread overview]
Message-ID: <X+kURC9LmmFz5Ks7@jasmine.lan> (raw)
In-Reply-To: <2C14BF51-2755-4315-AC75-26F71F93884D@vodafonemail.de>
On Sun, Dec 27, 2020 at 04:00:23PM +0100, Stefan wrote:
> Qemu is invoked with these arguments concerning random:
>
> -cpu host,+smap,+rdseed,+erms,+smep,+fsgsbase,+3dnowprefetch,+rdtscp,+pdpe1gb,+rdrand,+osxsave,+xsave,+tsc-deadline,+movbe,+x2apic,+pdcm,+xtpr,+tm2,+est,+vmx,+ds_cpl,+dtes64,+pclmuldq,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme -object rng-random,id=objrng0,filename=/dev/random -device virtio-rng-pci,rng=objrng0,id=rng0,bus=pci.0,addr=0x1c
What does the argument "filename=/dev/random" do? Does it use the host's
/dev/random to provide entropy to the QEMU guest?
next prev parent reply other threads:[~2020-12-27 23:11 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 [this message]
2020-12-27 23:28 ` Stefan
2020-12-29 2:51 ` Leo Famulari
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+kURC9LmmFz5Ks7@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).