From: Paolo Bonzini <pbonzini@redhat.com>
To: David Vrabel <david.vrabel@citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Andy Lutomirski <luto@amacapital.net>,
Linux Virtualization <virtualization@lists.linux-foundation.org>
Cc: Mathew John <mathewj@microsoft.com>,
Theodore Ts'o <tytso@mit.edu>, Jim Mattson <jmattson@vmware.com>,
kvm list <kvm@vger.kernel.org>, Gleb Natapov <gleb@kernel.org>,
Niels Ferguson <niels@microsoft.com>,
Doug Covelli <dcovelli@vmware.com>,
David Hepkin <davidhep@microsoft.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Jake Oshins <jakeo@microsoft.com>,
xen-devel@lists.xenproject.org,
Alok Kataria <akataria@vmware.com>,
John Starks <John.Starks@microsoft.com>
Subject: Re: [Xen-devel] [RFC] Hypervisor RNG and enumeration
Date: Wed, 29 Oct 2014 15:01:13 +0100 [thread overview]
Message-ID: <5450F329.2090105@redhat.com> (raw)
In-Reply-To: <5450F234.6040302@citrix.com>
On 10/29/2014 02:57 PM, David Vrabel wrote:
> Microsoft already has a specification to obtain a random number via an
> ACPI device. The VM Generation ID.
>
> http://www.microsoft.com/en-us/download/details.aspx?id=30707
That's a very different thing. The VM Generation ID always returns the
same number if you run the VM from the same configuration file.
It tells the VM when it might need a reseed, but provides neither a best
effort random number like this spec does, nor an entropy source like
virtio-rng does.
Paolo
next prev parent reply other threads:[~2014-10-29 14:01 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 5:19 [RFC] Hypervisor RNG and enumeration Andy Lutomirski
2014-10-29 10:37 ` [Xen-devel] " Andrew Cooper
2014-10-29 13:45 ` Paolo Bonzini
2014-10-29 13:57 ` David Vrabel
2014-10-29 14:01 ` Paolo Bonzini [this message]
2014-10-29 14:01 ` Paolo Bonzini
2014-10-29 13:57 ` David Vrabel
2014-10-29 13:45 ` Paolo Bonzini
2014-10-29 16:07 ` H. Peter Anvin
2014-10-29 16:07 ` H. Peter Anvin
2014-10-29 16:07 ` [Xen-devel] " H. Peter Anvin
2014-10-29 16:23 ` Andy Lutomirski
2014-10-29 16:23 ` [Xen-devel] " Andy Lutomirski
2014-10-29 16:07 ` H. Peter Anvin
2014-10-29 16:07 ` H. Peter Anvin
2014-10-29 16:07 ` H. Peter Anvin
2014-10-29 10:37 ` Andrew Cooper
2014-10-29 15:14 ` [Xen-devel] " Ian Jackson
2014-10-29 16:13 ` Andy Lutomirski
2014-10-29 16:13 ` [Xen-devel] " Andy Lutomirski
2014-10-29 16:29 ` Jake Oshins
2014-10-29 16:50 ` Andy Lutomirski
2014-10-29 16:50 ` [Xen-devel] " Andy Lutomirski
2014-10-29 18:22 ` Paolo Bonzini
2014-10-29 18:22 ` [Xen-devel] " Paolo Bonzini
2014-10-29 16:29 ` Jake Oshins
2014-10-29 15:14 ` Ian Jackson
2014-10-30 12:21 ` David Vrabel
2014-10-30 12:21 ` [Xen-devel] " David Vrabel
2014-10-30 12:25 ` Paolo Bonzini
2014-10-30 12:25 ` Paolo Bonzini
2014-10-30 14:45 ` [Xen-devel] " Andy Lutomirski
2014-10-30 15:12 ` Ian Campbell
2014-10-30 15:12 ` Ian Campbell
2014-10-30 14:45 ` Andy Lutomirski
2014-10-30 14:33 ` [Xen-devel] " Roger Pau Monné
2014-10-30 14:33 ` Roger Pau Monné
2014-10-30 14:33 ` [Xen-devel] " Roger Pau Monné
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=5450F329.2090105@redhat.com \
--to=pbonzini@redhat.com \
--cc=John.Starks@microsoft.com \
--cc=akataria@vmware.com \
--cc=andrew.cooper3@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=davidhep@microsoft.com \
--cc=dcovelli@vmware.com \
--cc=gleb@kernel.org \
--cc=hpa@zytor.com \
--cc=jakeo@microsoft.com \
--cc=jmattson@vmware.com \
--cc=kvm@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mathewj@microsoft.com \
--cc=niels@microsoft.com \
--cc=tytso@mit.edu \
--cc=virtualization@lists.linux-foundation.org \
--cc=xen-devel@lists.xenproject.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.