From: "Daniel P. Berrange" <berrange@redhat.com>
To: Amit Shah <amit.shah@redhat.com>
Cc: qemu list <qemu-devel@nongnu.org>,
Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] [PATCH v2 1/1] virtio-rng: hardware random number generator device
Date: Mon, 28 May 2012 09:33:57 +0100 [thread overview]
Message-ID: <20120528083357.GB19909@redhat.com> (raw)
In-Reply-To: <e04e5a79dc6c5143c53aba66cf226c97c8300343.1337972540.git.amit.shah@redhat.com>
On Sat, May 26, 2012 at 01:02:49AM +0530, Amit Shah wrote:
> The Linux kernel already has a virtio-rng driver, this is the device
> implementation.
>
> When the guest asks for entropy from the virtio hwrng, it puts a buffer
> in the vq. We then put entropy into that buffer, and push it back to
> the guest.
>
> The chardev connected to this device is fed the data to be sent to the
> guest.
>
> Invocation is simple:
>
> $ qemu ... -device virtio-rng-pci,chardev=foo
>
> In the guest, we see
>
> $ cat /sys/devices/virtual/misc/hw_random/rng_available
> virtio
>
> $ cat /sys/devices/virtual/misc/hw_random/rng_current
> virtio
>
> # cat /dev/hwrng
>
> Simply feeding /dev/urandom from the host to the chardev is sufficient:
>
> $ qemu ... -chardev socket,path=/tmp/foo,server,nowait,id=foo \
> -device virtio-rng,chardev=foo
>
> $ nc -U /tmp/foo < /dev/urandom
ACK to this ARGV design from a libvirt POV.
> A QMP event is sent for interested apps to monitor activity and send the
> appropriate number of bytes that get asked by the guest:
>
> {"timestamp": {"seconds": 1337966878, "microseconds": 517009}, \
> "event": "ENTROPY_NEEDED", "data": {"bytes": 64}}
IIUC, there are three ways mgmt apps can use the RNG with the
chardev
- Wire it up to a source that just blindly provides all the
entropy QEMU desires (as you /dev/urandom example above)
- Feed in a fixed amount of entropy every minute, regardless
of how much QEMU desires
- Feed in entropy on demand, in response to the ENTROPY_NEEDED
event notification (possibly throttling)
These options sounds like they should cover all reasonable needs,
so gets my vote. Probably want to include the ENTROPY_NEEDED
event in my patch which adds rate limiting to guest initiated
events.
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next prev parent reply other threads:[~2012-05-28 8:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 19:32 [Qemu-devel] [PATCH v2 0/1] virtio-rng: hardware random number generator Amit Shah
2012-05-25 19:32 ` [Qemu-devel] [PATCH v2 1/1] virtio-rng: hardware random number generator device Amit Shah
2012-05-25 20:00 ` Anthony Liguori
2012-05-25 20:20 ` Amit Shah
2012-06-04 11:04 ` Anthony Liguori
2012-06-05 9:41 ` Amit Shah
2012-06-05 9:54 ` Anthony Liguori
2012-06-05 10:16 ` Amit Shah
2012-06-11 13:34 ` Daniel P. Berrange
2012-05-28 8:33 ` Daniel P. Berrange [this message]
2012-05-28 9:17 ` Amit Shah
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=20120528083357.GB19909@redhat.com \
--to=berrange@redhat.com \
--cc=amit.shah@redhat.com \
--cc=anthony@codemonkey.ws \
--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).