All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Smith <andy@strugglers.net>
To: xen-devel@lists.xen.org
Subject: Re: [Xen Hackathon] new PV drivers
Date: Mon, 9 Jun 2014 19:16:19 +0000	[thread overview]
Message-ID: <20140609191619.GZ21583@bitfolk.com> (raw)
In-Reply-To: <1402326385.23103.10.camel@kazak.uk.xensource.com>

Hello,

On Mon, Jun 09, 2014 at 04:06:25PM +0100, Ian Campbell wrote:
> On Mon, 2014-06-09 at 10:55 -0400, Boris Ostrovsky wrote:
> > Feeding is done by interrupt timing and block device access latency, 
> > both of which are happening in a guest. I don't know whether there is 
> > enough of that but perhaps before embarking on new PV driver it may be 
> > worth investigating quality of existing entropy source. Or maybe it's 
> > already been looked at.
> 
> I've not done the numbers/investigated it myself but it's a quite widely
> held belief that those things are not sufficient in a virtual machine. 

Available entropy in my VMs is much lower than on the dom0, to the
point where I had customers doing a lot of HTTPS/TLS who were
expeirencing stalls.

I bought a couple of Entropy Keys and shipped in entropy to the VMs
via an additional daemon.

    https://tools.bitfolk.com/wiki/Entropy

A software solution to seed entropy in VMs from the dom0's pool
would be welcome.

Cheers,
Andy

      reply	other threads:[~2014-06-09 19:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-03 11:47 [Xen Hackathon] new PV drivers Stefano Stabellini
2014-06-06 13:56 ` Anil Madhavapeddy
2014-06-08  0:02   ` Adam Wick
2014-06-09  9:02   ` Ian Campbell
2014-06-09  9:42     ` Stefano Stabellini
2014-06-09  9:45       ` Ian Campbell
2014-06-09 14:30       ` Boris Ostrovsky
2014-06-09 14:33         ` Ian Campbell
2014-06-09 14:39           ` Boris Ostrovsky
2014-06-09 14:43             ` Ian Campbell
2014-06-09 14:55               ` Boris Ostrovsky
2014-06-09 15:06                 ` Ian Campbell
2014-06-09 19:16                   ` Andy Smith [this message]

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=20140609191619.GZ21583@bitfolk.com \
    --to=andy@strugglers.net \
    --cc=xen-devel@lists.xen.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 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.