From: Dor Laor <dlaor@redhat.com>
To: Vadim Rozenfeld <vrozenfe@redhat.com>
Cc: Avi Kivity <avi@redhat.com>, "--[ UxBoD ]--" <uxbod@splatnix.net>,
kvm@vger.kernel.org
Subject: Re: KVM, Entropy and Windows
Date: Thu, 17 Feb 2011 12:37:54 +0200 [thread overview]
Message-ID: <4D5CFA82.6000708@redhat.com> (raw)
In-Reply-To: <1297937344.2435.12.camel@localhost>
On 02/17/2011 12:09 PM, Vadim Rozenfeld wrote:
> On Thu, 2011-02-17 at 11:11 +0200, Avi Kivity wrote:
>> On 02/16/2011 09:54 PM, --[ UxBoD ]-- wrote:
>>> Hello all,
>>>
>>> I believe I am hitting a problem on one of our Windows 2003 KVM guests were I believe it is running out of Entropy and causing SSL issues.
>>>
>>> I see that there is a module called virtio-rng which I believe passes the HW entropy source through to the guest but does this work on Windows as-well ?
>>>
>>
>> AFAIK there is no Windows driver for virtio-rng. Seems like a good
>> idea. Vadim?
> virtio-rng driver for windows is not a big deal. IMO, the real problem
> will be to force Windows to use for CriptoApi.
What's the implication of it? good or bad?
Do you know what hyper-v is doing for it?
>>
>>> If it doesn't any ideas on how I can increase the amount of entropy being generated on a headless system ? or even monitor entropy on a Windows system ?
>>
>> No idea. Maybe you could ask Windows to collect entropy from packet
>> timings.
>>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-02-17 10:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 19:54 KVM, Entropy and Windows --[ UxBoD ]--
2011-02-17 9:11 ` Avi Kivity
2011-02-17 10:09 ` Vadim Rozenfeld
2011-02-17 10:37 ` Dor Laor [this message]
2011-02-17 11:09 ` Vadim Rozenfeld
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=4D5CFA82.6000708@redhat.com \
--to=dlaor@redhat.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=uxbod@splatnix.net \
--cc=vrozenfe@redhat.com \
/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.