SEND US FEEDBACK!
vSphere API/SDK Documentation > vSphere Management SDK > vSphere Web Services SDK Documentation > VMware vSphere API Reference > Data Object Types > H
  • 0 Ratings

Data Object - HostCpuIdInfo(vim.host.CpuIdInfo)

Property of
ClusterEVCManagerEVCState, EVCMode, GuestOsDescriptor, HostCapability, HostCpuPackage, HostHardwareInfo, VirtualMachineConfigInfo, VirtualMachineCpuIdInfoSpec
Extends
DynamicData

Data Object Description

The CpuIdInfo data object type is used to represent the CPU features of a particular host or product, or to specify what the CPU feature requirements are for a particular virtual machine or guest operating system.

As of vSphere API 5.1 FeatureMask must be used for masking all hosts and is the recommended method for masking virtual machines with hardware version 9 and above (newer). CpuIdInfo should be used only to mask hardware version 8 and lower (older) virtual machines. Although CpuIdInfo can mask all virtual machines regardless of hardware version, its application is limited and has been superceded by FeatureMask.

For each register (eax,ebx,ecx,edx), the string is a bit mask of the form:

       ????:????:????:????:????:????:????:????
   

When used to represent the features of a specific processor package (cpuPkg), the features common to all processors on a host (cpuFeature), or the features supported by a virtualization platform (supportedCpuFeature), each bit is either '0' or '1', or '-' for unknown/unspecified. In these feature vectors, the vendor field is never set.

Optional values in these feature vectors default to '----:----:----:----:----:----:----:----'.

When specifying the required feature set for a virtual machine or a guest operating system, the bits can take on the values as described below, and the vendor field may be set. The total feature requirements for a virtual machine are composed by using any requirements listed in the virtual machine's configuration to override the requirements listed in the descriptor for the virtual machine's guest OS.

Bits used for specifying requirements:

The values 'F' and '1' are rarely used but included for completeness. The '0' and '1' values do not promise a faithful virtualization of these features; whether the features work when forced to 0 or 1 is highly dependent on the guest software.

Optional values in the requirements from the virtual machine's configuration default to '----:----:----:----:----:----:----:----'. Optional values in the requirements from the guest OS descriptor default to 'xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx'.

Once the feature requirements for a virtual machine have been composed from the virtual machine's configuration and guest OS descriptor, the bit types above are used to identify whether or not the virtual machine can be powered on or be migrated with VMotion to a particular host. The rules are as follows:

Properties

Name Type Description
eax*xsd:string

String representing the required EAX bits.
ebx*xsd:string

String representing the required EBX bits.
ecx*xsd:string

String representing the required ECX bits.
edx*xsd:string

String representing the required EDX bits.
levelxsd:int

Level (EAX input to CPUID).
vendor*xsd:string

Used if this mask is for a particular vendor.
Properties inherited from DynamicData
None
*Need not be set
Show WSDL type definition




Feedback

  • 0 Ratings