VMware_OVFTool_x64

VMware OVF Tool 2.1.0 System Requirements ----------------------- VMware OVF Tool is supported on the following operating systems: Windows 32-bit (x86) and 64-bit (x86_x64) Windows XP Windows 2003 Windows Vista Windows 2008 Windows 7 Linux 32-bit (x86) and 64-bit (x86_x64) CentOS 5.x 6.x Fedora Core 13.x 14.x 15.x RedHat Enterprise Linux (RHEL) 5.x 6.x SUSE Enterprise Server 10.x 11.x Ubuntu Desktop 9.x 10.x 11.x Mac OS X: Mac OS X 10.6 Mac Os X 10.7 Changes since 2.0.1 ------------------- . support for vCloud as both a source and a target. . Enhanced integration support (--machineMode). . Support for vSphere 5.0. . Improved lax mode support. . Improved error reports. Changes since 2.0.0 ------------------- . Fixed bug that caused OVF Tool not to work with the "Import from vSphere" feature on the VMware Virtual Appliance Marketplace. . Fixed launch issue on Linux/Mac if installed in a location where the path includes spaces. . Fixed issue with properties when importing to vApprun workspace. Changes since 1.0.1 ------------------- . Support for the OVF 1.1 specification. . Support for OVF packages that includes ISO and floppy images. . Support for vApprun as target and source (see http://labs.vmware.com/flings/vapprun). . Support for OVF Tool on the Mac OS X operating system (Intel-only). . A lax mode (--lax) that enables a best-effort conversion of OVF packages which do not fully conform to the OVF standard or include virtual hardware that is not supported by the destination. For example, VirtualBox (version 3.0 and 3.1) produced OVF packages can be converted in lax mode. . Bug fix for handling vmxnet3 targets. FAQ ------------------ -Q: How do I use OVF Tool with VMware Server 2.0.x? A: VMware Server 2.0.x default port is 8333. To connect to a VMware Server 2.0 host use vi://username:password@hostname:8333/ as target/source. Q: What type of X.509 certificates does OVF Tool use? A: X509 certicates used for OVF Tool must be properly formatted so that each line in the base64 encoding is 64 characters long except the last line which may be shorter. This conforms to RFC 1421(cf. page 12, http://www.ietf.org/rfc/rfc1421.txt). Q: Can I use the OVF Tool on the ESX Service Console? A: Yes. However, you must use a VI locator as a target (use localhost as the host), and specify the username/password for the host. Using a file target (i.e., a file path directly to a VMFS volume) will generate files that are incompatible with ESX. Q: Can I use OVF tool on an ESX host to backup a VMX file? A: Yes, but you have to use a VI source locator to export the virtual machine to an OVF package. Do not use OVF Tool directly on the VMX files on a VMFS filesystem. Q: In what formats are the locators encoded? A: The locators are URI encoded so special characters should be escaped as done in URIs. The special characters are escaped using % and their ASCII hex value. For instance, if you use a "@" in your password it should be escaped with %40 as in vi://foo:b%40r@hostname. Q: Which versions of vSphere support OVF packages with ISO/floppy images? A: vSphere 4.1 and later. You can use the flag --noImageFiles to ignore upload of ISO and floppy image files for older versions of vSphere. For More Information ----------------------- For more information about VMware OVF Tool, see http://www.vmware.com/go/ovf/ Follow the vApp blog on http://blogs.vmware.com/vapp/ ---------------------------------------------------------------------- Copyright 2011 VMware, Inc. All rights reserved.