The VM-Series is delivered as a file in the Open Virtualization
Alliance (OVA) format. The OVA image is downloaded as a zip archive
that is expanded into three files. If you are having trouble deploying
the OVA image, make sure the three files are unpacked and present
and, if necessary, download and extract the OVA image again.
The ovf extension is for the OVF descriptor file that
contains all metadata about the package and its contents.
The mf extension is for the OVF manifest file that contains
the SHA-1 digests of individual files in the package.
The vmdk extension is for the virtual disk image file.
The virtual disk in the OVA image is large for the VM-Series;
this file is nearly 900MB and must be present on the computer running
the vSphere client or must be accessible as a URL for the OVA image.
Make sure the network connection is sufficient between the vSphere
client computer and the target ESXi host. Any firewalls in the path
will need to allow TCP ports 902 and 443 from the vSphere client
to the ESXi host(s).There needs to be sufficient bandwidth and low
latency on the connection otherwise the OVA deployment can take
hours or timeout and fail.
ESX 6.5.0a build 4887370 limits you to 2 CPU cores per
socket. If you are deploying a VM-300, VM-500 or VM-700 to which
you want to allocate more than 2 vCPUs per socket, refer to the
VMware KB: https://kb.vmware.com/s/article/53354, for a workaround.