All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Burton, Ross" <ross.burton@intel.com>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] qemu.inc: Drop rng-tools
Date: Wed, 15 Nov 2017 12:26:22 +0000	[thread overview]
Message-ID: <CAJTo0LYfAYZruf=9WYFqD2ae2==LdTGwayFeXPxtQ7ROPm-T2w@mail.gmail.com> (raw)
In-Reply-To: <CAP9ODKow3s0rXMmkVYM5b5jsgG-70GnXZkHMK1WxaFSUTA-c2A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 572 bytes --]

On 14 November 2017 at 17:16, Otavio Salvador <
otavio.salvador@ossystems.com.br> wrote:

> Hello Ross,
>
> On Mon, Nov 13, 2017 at 5:55 PM, Burton, Ross <ross.burton@intel.com>
> wrote:
> > Can you explain why?
>
> We are using QEMU ARM for runtime tests on CI for updatehub, on this,
> when we run something that required entropy just after boot and
> especially if running inside of a Docker, it fails badly for 140s.
> Adding rng-tools solves it :-)


Are you enabling the virtio-rng driver so qemu can bridge the host entropy
into the guest?

Ross

[-- Attachment #2: Type: text/html, Size: 973 bytes --]

  reply	other threads:[~2017-11-15 12:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-13 17:35 [PATCH] qemu.inc: Drop rng-tools Richard Purdie
2017-11-13 19:30 ` Otavio Salvador
2017-11-13 19:55   ` Burton, Ross
2017-11-14 17:16     ` Otavio Salvador
2017-11-15 12:26       ` Burton, Ross [this message]
2017-11-15 19:59         ` Otavio Salvador
2017-11-16 13:11           ` Burton, Ross
2017-11-16 13:14             ` Richard Purdie
2017-11-16 13:26               ` Otavio Salvador
2018-11-22 17:39                 ` Martin Jansa
2018-11-22 17:48                   ` Otavio Salvador
  -- strict thread matches above, loose matches on Subject: below --
2017-11-13 17:34 Richard Purdie

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='CAJTo0LYfAYZruf=9WYFqD2ae2==LdTGwayFeXPxtQ7ROPm-T2w@mail.gmail.com' \
    --to=ross.burton@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio.salvador@ossystems.com.br \
    /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 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.