# Data Object - HostSubSpecification(vim.profile.host.HostSubSpecification)

Property of
  HostSpecification
Parameter to
  UpdateHostSubSpecification
Extends
  DynamicData
Since
  vSphere API 6.5

## Data Object Description

Host sub specification data are the data used when create a virtual device, and/or configure the virtual device and its related host services. A typical example of host sub specification data is the DVS host view specification, which is used when create DVS host view on an ESXi host and configure the virtual switch on the host. The introduction of this type of data is for improving the availability of the ESXi host management. For example, when the VirtualCenter server is not available, an ESXi host will have enough information to reconfigure DVS host view properly when the ESXi host is booted from stateless or stateless caching. Host sub specification data are data for VMware internal data structure used in virtual device creation and configuration. They are different to AnswerFile which are from public knowledge domain or the public API of VMware ESXi host services. When the host sub specification data for a single feature are stored in multiple host sub specification data objects, it is the responsibility of the host specification source in this feature to guarantee the completeness and consistency of these host sub specification objects.

Properties

Name | Type | Description
--- | --- | ---
binaryData* | xsd:base64Binary | The host sub specification data in Binary for wire efficiency. Since vSphere API 6.7
createdTime | xsd:dateTime | Time at which the host sub specification was created.
data* | xsd:byte[] | The host sub specification data
name | xsd:string | The full name of the host sub specification. The format of this member variable is: CompanyName_ProductName_SubSpecName. Thus, name conflict is avoided by containing the `company name`, `product name`, and `sub specification name` in this full name.
Properties inherited from DynamicData
None

*Need not be set
Show WSDL type definition
<complexType xmlns="http://www.w3.org/2001/XMLSchema" xmlns:vsan="urn:vsan" name="HostSubSpecification"> <complexContent> <extension base="vsan:DynamicData"> <sequence> <element name="name" type="xsd:string"/> <element name="createdTime" type="xsd:dateTime"/> <element name="data" type="xsd:byte" minOccurs="0" maxOccurs="unbounded"/> <element name="binaryData" type="xsd:base64Binary" minOccurs="0"/> </sequence> </extension> </complexContent> </complexType>