qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: qemu-devel@nongnu.org
Cc: Amit Shah <amit.shah@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Andreas Faerber <afaerber@suse.de>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: [Qemu-devel] [PATCH 0/8] add paravirtualization hwrng support (v3)
Date: Wed, 31 Oct 2012 17:00:26 -0500	[thread overview]
Message-ID: <1351720834-22805-1-git-send-email-aliguori@us.ibm.com> (raw)

Hi,

This series implements the backend and frontend infrastructure for virtio-rng.
This is similar to previous series sent out by both Amit and myself although
it has been trimmed down considerably.

In terms of backends, a file and EGD backend are supported.  The file defaults
to /dev/random based on the feedback from Peter.  It's still possible to
support /dev/urandom though as an entropy source by overriding the file name.

v1 -> v2:
 - Include default backend patch from separate series
 - Add a rate limiting patch
v2 -> v3:
 - Small bug fix spotted by Paolo

My take away from all of the various discussions on what the Right Way to
use virtio-rng is:

 1) /dev/random should always be used as the entropy source (I've left it
    configurable though)

 2) I think the Right Way to configure virtio-rng is to figure out what the
    available entropy is on the host, and then decide how to allocate that
    to each guest.  As such, I've implemented rate limiting.

    I think QEMU is the right place to do this because this is a property of
    specific virtual machines.  I can imagine a cloud provider wanting to
    guarantee a certain level of entropy for different classes of VMs.  Even
    if rngd could be used to do this, configuring it differently for different
    guests would be cumbersome.

 3) `qemu -device virtio-rng-pci` will Just Work but risks exhausting host
    entropy.  This means we can't make it the default for machines.  But for
    most command line users, I think this is the behavior they want.

             reply	other threads:[~2012-10-31 22:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-31 22:00 Anthony Liguori [this message]
2012-10-31 22:00 ` [Qemu-devel] [PATCH 1/8] vl: add -object option to create QOM objects from the command line Anthony Liguori
2012-10-31 22:00 ` [Qemu-devel] [PATCH 2/8] object: add object_property_add_bool (v2) Anthony Liguori
2012-10-31 22:00 ` [Qemu-devel] [PATCH 3/8] rng: add RndBackend abstract object class Anthony Liguori
2012-10-31 22:00 ` [Qemu-devel] [PATCH 4/8] rng-random: add an RNG backend that uses /dev/random (v3) Anthony Liguori
2012-10-31 22:00 ` [Qemu-devel] [PATCH 5/8] rng-egd: introduce EGD compliant RNG backend Anthony Liguori
2012-10-31 22:00 ` [Qemu-devel] [PATCH 6/8] virtio-rng: hardware random number generator device Anthony Liguori
2012-10-31 22:00 ` [Qemu-devel] [PATCH 7/8] virtio-rng: add rate limiting support Anthony Liguori
2012-10-31 22:00 ` [Qemu-devel] [PATCH 8/8] virtio-rng-pci: create a default backend if none exists Anthony Liguori

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=1351720834-22805-1-git-send-email-aliguori@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=afaerber@suse.de \
    --cc=amit.shah@redhat.com \
    --cc=hpa@zytor.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.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 NNTP newsgroup(s).