VMware OVF Tool Release Notes
New Features in This Release
This software supports Open Virtualization Format (OVF) packages created with previous versions of the OVF Tool, and produces files compatible with OVF specifications 1.0 and 0.9. OVF Tool 4.2 has some new features including many that emphasize security.
System Requirements for OVF Tool
The OVF Tools supports the following operating systems and software.
Supported Operating Systems
The OVF Tool supports the following Windows 32-bit (x86) and 64-bit (x86_64) operating systems:
The OVF Tool supports the following Linux operating systems:
The OVF Tool supports the following Mac OS X 64-bit operating systems:
Supported VMware Products and Platforms
Version 4.2 of the OVF Tool supports the following VMware software:
OVF support is built into the vSphere (Web) Client that installs from vCenter Server. It is compatible with vSphere and ESXi hosts. Newer versions of vSphere supply later versions of the OVF Tool. ESXi and vCenter Server versions older than 5.5 are deprecated; the next release will not support them.
Space Requirements for OVF Packages
A virtual machine is stored as a set of files on disk. In the VMware runtime format, these files have extensions .vmx, .vmdk, .vmsd, .vmxf, and .nvram. The VMware hypervisor requires these file formats, which are optimized for efficient execution. An ESXi host often uses fully allocated flat disks in a VMFS file system to optimize virtual machine performance.
The OVF standard supports efficient, secure distribution of vApps and virtual machine templates. OVF is optimized for these goals, rather than for efficient runtime execution. OVF does not include specific information on runtime disk format because such information is not required until the virtual machine is deployed. When you package appliances with OVF, you can optimize one vApp for high performance in a production environment, and optimize another for minimal storage space during evaluation.
The following table contrasts a virtual machine in VMware file format with a virtual machine in OVF format. OVF employs a compressed sparse format for VMDK files. Virtual disks in that format cannot be used directly for execution without conversion.
Installing the OVF Tool
Download the Installer
Complete the Installation Steps
Follow this procedure for all installations:
Running the OVF Tool from a Windows Command Line
After installing the OVF Tool on Windows, you can run the OVF Tool from the Windows command line.
If you have the OVF Tool folder in your Path environment variable, you can run the OVF Tool from the command line.
Adding the OVF Tool to your Path Environment Variable
The following instructions are for Windows 7, but the steps are similar on other Windows systems.
Known Issues in This Version
The ovftool option --allowAllExtraConfig is no longer supported. The command-line option --allowAllExtraConfig never worked as designed. As of release 6.5 U1, vSphere no longer supports this option. The workaround is to use --allowExtraConfig instead to import additional configurations.
The OVF Tool supports OVF specifications 0.9 and 1.0, but does not support OVF specification 2.0 (not to be confused with OVF Tool version 2.0). For workarounds to allow import of VirtualBox OVF 2.0, see this web page.
The ovftool --proxy=proxy.example.com option should work, but when used within vSphere, it does not. To make a network connection through the proxy server, you must add the --X:viUseProxy option as documented in the OVF Tool User's Guide.
You cannot use OVF Tool for deploying a VM to static DVS port groups. To work around this issue:
There are no deprecated features in version 4.2 of the OVF Tool, but support for Windows XP and Windows Server 2003 has been discontinued.