Displaying 7 results from an estimated 7 matches for "commonhvintf".
2014 Oct 29
0
[Xen-devel] [RFC] Hypervisor RNG and enumeration
...not being able to use
the features from the common specification. I guess what they'd do is
reinvent the RNG as a Viridian extension (if they need it).
You can certainly do CPUID(0x4F000000) even if HYPERVISOR=0. What you
get back is undefined, but in all likelihood it won't be the
"CommonHVIntf" string.
Paolo
2014 Oct 29
1
[Xen-devel] [RFC] Hypervisor RNG and enumeration
...features from the common specification. I guess what they'd do is
> reinvent the RNG as a Viridian extension (if they need it).
>
> You can certainly do CPUID(0x4F000000) even if HYPERVISOR=0. What you
> get back is undefined, but in all likelihood it won't be the
> "CommonHVIntf" string.
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
David
2014 Oct 29
1
[Xen-devel] [RFC] Hypervisor RNG and enumeration
...features from the common specification. I guess what they'd do is
> reinvent the RNG as a Viridian extension (if they need it).
>
> You can certainly do CPUID(0x4F000000) even if HYPERVISOR=0. What you
> get back is undefined, but in all likelihood it won't be the
> "CommonHVIntf" string.
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
David
2014 Oct 29
2
[Xen-devel] [RFC] Hypervisor RNG and enumeration
...X)
> and provide the CPUID leaf 4F000000H, containing:
>
> * CPUID.4F000000H.0H.EAX = max_commonhv_leaf
> * CPUID.4F000000H.0H.EBX = 0x6D6D6F43
> * CPUID.4F000000H.0H.ECX = 0x56486E6F
> * CPUID.4F000000H.0H.EDX = 0x66746e49
>
> EBX, ECX, and EDX form the string "CommonHVIntf" in little-endian ASCII.
While testing various nested combinations, XenServer has found that
modern Windows 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 provi...
2014 Oct 29
2
[Xen-devel] [RFC] Hypervisor RNG and enumeration
...X)
> and provide the CPUID leaf 4F000000H, containing:
>
> * CPUID.4F000000H.0H.EAX = max_commonhv_leaf
> * CPUID.4F000000H.0H.EBX = 0x6D6D6F43
> * CPUID.4F000000H.0H.ECX = 0x56486E6F
> * CPUID.4F000000H.0H.EDX = 0x66746e49
>
> EBX, ECX, and EDX form the string "CommonHVIntf" in little-endian ASCII.
While testing various nested combinations, XenServer has found that
modern Windows 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 provi...
2014 Oct 29
11
[RFC] Hypervisor RNG and enumeration
...pervisor bit (bit 31 in CPUID.1H.0H.ECX)
and provide the CPUID leaf 4F000000H, containing:
* CPUID.4F000000H.0H.EAX = max_commonhv_leaf
* CPUID.4F000000H.0H.EBX = 0x6D6D6F43
* CPUID.4F000000H.0H.ECX = 0x56486E6F
* CPUID.4F000000H.0H.EDX = 0x66746e49
EBX, ECX, and EDX form the string "CommonHVIntf" in little-endian ASCII.
max_commonhv_leaf MUST be a number between 0x4F000000 and 0x4FFFFFFF. It
indicates the largest leaf defined in this specification that is provided.
Any leaves described in this specification with EAX values that exceed
max_commonhv_leaf MUST be handled by guests as t...
2014 Oct 29
11
[RFC] Hypervisor RNG and enumeration
...pervisor bit (bit 31 in CPUID.1H.0H.ECX)
and provide the CPUID leaf 4F000000H, containing:
* CPUID.4F000000H.0H.EAX = max_commonhv_leaf
* CPUID.4F000000H.0H.EBX = 0x6D6D6F43
* CPUID.4F000000H.0H.ECX = 0x56486E6F
* CPUID.4F000000H.0H.EDX = 0x66746e49
EBX, ECX, and EDX form the string "CommonHVIntf" in little-endian ASCII.
max_commonhv_leaf MUST be a number between 0x4F000000 and 0x4FFFFFFF. It
indicates the largest leaf defined in this specification that is provided.
Any leaves described in this specification with EAX values that exceed
max_commonhv_leaf MUST be handled by guests as t...