search for: commonhv

Here's a draft CommonHV spec. It's also on github: https://github.com/amluto/CommonHV So far, this provides a two-way RNG interface, a way to detect it, and a way to detect other hypervisor leaves. The latter is because, after both the enormous public thread and some private discussions, it seems that detection of...

Here's a draft CommonHV spec. It's also on github: https://github.com/amluto/CommonHV So far, this provides a two-way RNG interface, a way to detect it, and a way to detect other hypervisor leaves. The latter is because, after both the enormous public thread and some private discussions, it seems that detection of...

On 29/10/14 05:19, Andy Lutomirski wrote: > Here's a draft CommonHV spec. It's also on github: > > https://github.com/amluto/CommonHV > > So far, this provides a two-way RNG interface, a way to detect it, and > a way to detect other hypervisor leaves. The latter is because, after > both the enormous public thread and some private discussions...

On 29/10/14 05:19, Andy Lutomirski wrote: > Here's a draft CommonHV spec. It's also on github: > > https://github.com/amluto/CommonHV > > So far, this provides a two-way RNG interface, a way to detect it, and > a way to detect other hypervisor leaves. The latter is because, after > both the enormous public thread and some private discussions...

Andy Lutomirski writes ("[Xen-devel] [RFC] Hypervisor RNG and enumeration"): > Here's a draft CommonHV spec. It's also on github: > https://github.com/amluto/CommonHV This a worthwhile direction to investigate, and an interesting proposal. From a Xen point of view I have some concerns, though. I think in Xen we would want to implement the bulk of the provision of random numbers to guests...

On Thu, Oct 30, 2014 at 5:21 AM, David Vrabel <david.vrabel at citrix.com> wrote: > On 29/10/14 05:19, Andy Lutomirski wrote: >> CPUID leaf 4F000002H: miscellaneous features >> -------------------------------------------- >> > [...] >> ### CommonHV RNG >> >> If CPUID.4F000002H.EAX is nonzero, then it contains an MSR index used to >> communicate with a hypervisor random number generator. This MSR is >> referred to as MSR_COMMONHV_RNG. >> >> rdmsr(MSR_COMMONHV_RNG) returns a 64-bit best-effort random number....

On Thu, Oct 30, 2014 at 5:21 AM, David Vrabel <david.vrabel at citrix.com> wrote: > On 29/10/14 05:19, Andy Lutomirski wrote: >> CPUID leaf 4F000002H: miscellaneous features >> -------------------------------------------- >> > [...] >> ### CommonHV RNG >> >> If CPUID.4F000002H.EAX is nonzero, then it contains an MSR index used to >> communicate with a hypervisor random number generator. This MSR is >> referred to as MSR_COMMONHV_RNG. >> >> rdmsr(MSR_COMMONHV_RNG) returns a 64-bit best-effort random number....

On Oct 29, 2014 8:17 AM, "Ian Jackson" <Ian.Jackson at eu.citrix.com> wrote: > > Andy Lutomirski writes ("[Xen-devel] [RFC] Hypervisor RNG and enumeration"): > > Here's a draft CommonHV spec. It's also on github: > > https://github.com/amluto/CommonHV > > This a worthwhile direction to investigate, and an interesting > proposal. From a Xen point of view I have some concerns, though. > > I think in Xen we would want to implement the bulk of the provision...

On Oct 29, 2014 8:17 AM, "Ian Jackson" <Ian.Jackson at eu.citrix.com> wrote: > > Andy Lutomirski writes ("[Xen-devel] [RFC] Hypervisor RNG and enumeration"): > > Here's a draft CommonHV spec. It's also on github: > > https://github.com/amluto/CommonHV > > This a worthwhile direction to investigate, and an interesting > proposal. From a Xen point of view I have some concerns, though. > > I think in Xen we would want to implement the bulk of the provision...

...s Server versions must have the hypervisor bit hidden from > them for them to be happy running HyperV, despite the fact that they > will make use of the Viridian virtual extensions also provided. Right. > As a result, while it is certainly advisable for the hypervisor bit to > be set, CommonHV should be available to be found by paravirtualised > drivers inside an OS which can't cope with the hypervisor bit set. Microsoft should just stop putting arbitrary limitations on their software; or pay the price which, in this case, is not being able to use the features from the common spe...

...hypervisor bit hidden from >> them for them to be happy running HyperV, despite the fact that they >> will make use of the Viridian virtual extensions also provided. > > Right. > >> As a result, while it is certainly advisable for the hypervisor bit to >> be set, CommonHV should be available to be found by paravirtualised >> drivers inside an OS which can't cope with the hypervisor bit set. > > Microsoft should just stop putting arbitrary limitations on their > software; or pay the price which, in this case, is not being able to use > the feat...

On 29/10/14 05:19, Andy Lutomirski wrote: > CPUID leaf 4F000002H: miscellaneous features > -------------------------------------------- > [...] > ### CommonHV RNG > > If CPUID.4F000002H.EAX is nonzero, then it contains an MSR index used to > communicate with a hypervisor random number generator. This MSR is > referred to as MSR_COMMONHV_RNG. > > rdmsr(MSR_COMMONHV_RNG) returns a 64-bit best-effort random number. If the > hypervis...

...hypervisor bit hidden from >> them for them to be happy running HyperV, despite the fact that they >> will make use of the Viridian virtual extensions also provided. > > Right. > >> As a result, while it is certainly advisable for the hypervisor bit to >> be set, CommonHV should be available to be found by paravirtualised >> drivers inside an OS which can't cope with the hypervisor bit set. > > Microsoft should just stop putting arbitrary limitations on their > software; or pay the price which, in this case, is not being able to use > the feat...