| 1 | <?xml version='1.0' encoding='UTF-8'?>
|
|---|
| 2 | <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
|
|---|
| 3 | <topic xml:lang="en-us" id="ovf-about">
|
|---|
| 4 | <title>About the OVF Format</title>
|
|---|
| 5 |
|
|---|
| 6 | <body>
|
|---|
| 7 | <p>OVF is a cross-platform standard supported by many virtualization products which enables the creation of
|
|---|
| 8 | ready-made virtual machines that can then be imported into a hypervisor such as <ph
|
|---|
| 9 | conkeyref="vbox-conkeyref-phrases/product-name"/>. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> makes
|
|---|
| 10 | OVF import and export easy to do, using <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> or the command-line
|
|---|
| 11 | interface. </p>
|
|---|
| 12 | <p>Using OVF enables packaging of <i>virtual appliances</i>. These are disk images, together with configuration
|
|---|
| 13 | settings that can be distributed easily. This way one can offer complete ready-to-use software packages, including
|
|---|
| 14 | OSes with applications, that need no configuration or installation except for importing into <ph
|
|---|
| 15 | conkeyref="vbox-conkeyref-phrases/product-name"/>. </p>
|
|---|
| 16 | <note>
|
|---|
| 17 | <p>The OVF standard is complex, and support in <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is an ongoing process. No guarantee is made that <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports all appliances created by other virtualization software. In particular, the following limitations exist:</p>
|
|---|
| 18 | <p>
|
|---|
| 19 | <ul>
|
|---|
| 20 | <li>
|
|---|
| 21 | <p>OVF localization, with multiple languages in a single OVF file, is not yet supported.</p>
|
|---|
| 22 | </li>
|
|---|
| 23 | <li>
|
|---|
| 24 | <p>Some OVF sections like StartupSection, DeploymentOptionSection, and InstallSection are ignored.</p>
|
|---|
| 25 | </li>
|
|---|
| 26 | <li>
|
|---|
| 27 | <p>OVF environment documents, including their property sections are not yet supported.</p>
|
|---|
| 28 | </li>
|
|---|
| 29 | <li>
|
|---|
| 30 | <p>Remote files using HTTP or other mechanisms are not yet supported.</p>
|
|---|
| 31 | </li>
|
|---|
| 32 | </ul>
|
|---|
| 33 | </p>
|
|---|
| 34 | </note>
|
|---|
| 35 | <p>Appliances in OVF format can appear in the following variants: </p>
|
|---|
| 36 | <ul>
|
|---|
| 37 | <li>
|
|---|
| 38 | <p>They can come in several files, as one or several disk images, typically in the widely-used VMDK format. See
|
|---|
| 39 | <xref href="vdidetails.dita"/>. They also include a textual description file in an XML dialect with an
|
|---|
| 40 | <filepath>.ovf</filepath> extension. These files must then reside in the same directory for <ph
|
|---|
| 41 | conkeyref="vbox-conkeyref-phrases/product-name"/> to be able to import them. </p>
|
|---|
| 42 | </li>
|
|---|
| 43 | <li>
|
|---|
| 44 | <p>Alternatively, the above files can be packed together into a single archive file, typically with an
|
|---|
| 45 | <filepath>.ova</filepath> extension. Such archive files use a variant of the TAR archive format and can
|
|---|
| 46 | therefore be unpacked outside of <ph conkeyref="vbox-conkeyref-phrases/product-name"/> with any utility that
|
|---|
| 47 | can unpack standard TAR files. </p>
|
|---|
| 48 | </li>
|
|---|
| 49 | </ul>
|
|---|
| 50 | <note>
|
|---|
| 51 | <p>OVF cannot describe snapshots that were taken for a virtual machine. As a result, when you export a virtual
|
|---|
| 52 | machine that has snapshots, only the current state of the machine will be exported. The disk images in the
|
|---|
| 53 | export will have a <i>flattened</i> state identical to the current state of the virtual machine. </p>
|
|---|
| 54 | </note>
|
|---|
| 55 | </body>
|
|---|
| 56 |
|
|---|
| 57 | </topic>
|
|---|
