Skip to main content

VMware VM hardware version matrix with esxi versions

 

Virtual Hardware VersionProducts
18ESXi 7.0 U1 (7.0.1)
Fusion 12.x
Workstation Pro 16.x
Workstation Player 16.x
17ESXi 7.0  (7.0.0)
16Fusion 11.x
Workstation Pro 15.x
Workstation Player 15.x
15ESXi 6.7 U2
14ESXi 6.7
Fusion 10.x
Workstation Pro 14.x
Workstation Player 14.x
13ESXi 6.5
12Fusion 8.x
Workstation Pro 12.x
Workstation Player 12.x
11ESXi 6.0
Fusion 7.x
Workstation 11.x
Player 7.x
10ESXi 5.5
Fusion 6.x
Workstation 10.x
Player 6.x
9ESXi 5.1
Fusion 5.x
Workstation 9.x
Player 5.x
8ESXi 5.0
Fusion 4.x
Workstation 8.x
Player 4.x
7ESXi/ESX 4.x
Fusion 3.x
Fusion 2.x
Workstation 7.x
Workstation 6.5.x
Player 3.x
Server 2.x
6Workstation 6.0.x
4ESX 3.x
ACE 2.x
Fusion 1.x
Player 2.x
3 and 4ACE 1.x
Lab Manager 2.x
Player 1.x
Server 1.x
Workstation 5.x
Workstation 4.x
3ESX 2.x
GSX Server 3.x


Comments

Post a Comment

Popular posts from this blog

Deploy OVF fails Issues detected with selected template. Details: VALUE_ILLEGAL: No supported hardware versions among [virtualbox-2.2]; supported: [vmx-04, vmx-07, vmx-08, vmx-09, vmx-10, vmx-11, vmx-12, vmx-13, vmx-14, vmx-15, vmx-16, vmx-17, vmx-18, vmx-19].

 Error: While deploy using OVF file ,getting error as : Issues detected with selected template. Details: - -1:-1:VALUE_ILLEGAL: No supported hardware versions among [virtualbox-2.2]; supported: [vmx-04, vmx-07, vmx-08, vmx-09, vmx-10, vmx-11, vmx-12, vmx-13, vmx-14, vmx-15, vmx-16, vmx-17, vmx-18, vmx-19]. Solution: Open .OVF file and edit       <Info>Virtual hardware requirements for a virtual machine</Info>       <System>         <vssd:ElementName>Virtual Hardware Family</vssd:ElementName>         <vssd:InstanceID>0</vssd:InstanceID>         <vssd:VirtualSystemIdentifier>zabbix_appliance-6.2.7</vssd:VirtualSystemIdentifier>         <vssd:VirtualSystemType> virtualbox-2.2 </vssd:VirtualSystemType>       </System> to  vmx-19       <Info>Virtual hardware requireme...
Post a Comment
Read more

Change ESXi acceptane level of VIBs to community Supported

-When you install VIB bundles you may see issue like:               'Could not find a trusted signer: self signed certificate  For resolving this issue, we have to convert the ESXi to community supported acceptance level. -To do that: if  ESXI is a VM :      Edit settings ->boot option ->disable secure boot. if Physical ESXi:      Edit  UEFI Now ssh to ESXi: - Move the ESX machine to community-support esxcli software acceptance set --level=CommunitySupported - Install the bundle with no-sign-check esxcli software vib install -d  VMware_bootbank_vmware-fdm_7.0.1-16478307.vib --no-sig-check -  Set back PartnerSupported esxcli software acceptance set --level=PartnerSupported
Post a Comment
Read more