Changeset 105289 in vbox for trunk/doc/manual/en_US/dita/topics/ovf-about.dita
- Timestamp:
- Jul 12, 2024 9:07:43 AM (6 months ago)
- File:
-
- 1 edited
-
trunk/doc/manual/en_US/dita/topics/ovf-about.dita (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/manual/en_US/dita/topics/ovf-about.dita
r99797 r105289 5 5 6 6 <body> 7 <p> 8 OVF is a cross-platform standard supported by many 9 virtualization products which enables the creation of ready-made 10 virtual machines that can then be imported into a hypervisor 11 such as <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> makes OVF import and 12 export easy to do, using <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> or the command-line 13 interface. 14 </p> 15 <p> 16 Using OVF enables packaging of <i>virtual 17 appliances</i>. These are disk images, together with 18 configuration settings that can be distributed easily. This way 19 one can offer complete ready-to-use software packages, including 20 OSes with applications, that need no configuration or 21 installation except for importing into <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. 22 </p> 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> 23 16 <note> 24 <p> 25 The OVF standard is complex, and support in <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is 26 an ongoing process. In particular, no guarantee is made that 27 <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports all appliances created by other 28 virtualization software. For a list of known limitations, see 29 <xref href="KnownIssues.dita">Known Limitations</xref>. 30 </p> 17 <p>The OVF standard is complex, and support in <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is an ongoing 18 process. In particular, no guarantee is made that <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports 19 all appliances created by other virtualization software. For a list of known limitations, see <xref 20 href="KnownIssues.dita">Known Limitations</xref>. </p> 31 21 </note> 32 <p> 33 Appliances in OVF format can appear in the following variants: 34 </p> 22 <p>Appliances in OVF format can appear in the following variants: </p> 35 23 <ul> 36 24 <li> 37 <p> 38 They can come in several files, as one or several disk 39 images, typically in the widely-used VMDK format. See 40 <xref href="vdidetails.dita"/>. They also include a textual 41 description file in an XML dialect with an 42 <filepath>.ovf</filepath> extension. These files must then 43 reside in the same directory for <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to be able 44 to import them. 45 </p> 25 <p>They can come in several files, as one or several disk images, typically in the widely-used VMDK format. See 26 <xref href="vdidetails.dita"/>. They also include a textual description file in an XML dialect with an 27 <filepath>.ovf</filepath> extension. These files must then reside in the same directory for <ph 28 conkeyref="vbox-conkeyref-phrases/product-name"/> to be able to import them. </p> 46 29 </li> 47 30 <li> 48 <p> 49 Alternatively, the above files can be packed together into a 50 single archive file, typically with an 51 <filepath>.ova</filepath> extension. Such archive files use 52 a variant of the TAR archive format and can therefore be 53 unpacked outside of <ph conkeyref="vbox-conkeyref-phrases/product-name"/> with any utility that can 54 unpack standard TAR files. 55 </p> 31 <p>Alternatively, the above files can be packed together into a single archive file, typically with an 32 <filepath>.ova</filepath> extension. Such archive files use a variant of the TAR archive format and can 33 therefore be unpacked outside of <ph conkeyref="vbox-conkeyref-phrases/product-name"/> with any utility that 34 can unpack standard TAR files. </p> 56 35 </li> 57 36 </ul> 58 37 <note> 59 <p> 60 OVF cannot describe snapshots that were taken for a virtual 61 machine. As a result, when you export a virtual machine that 62 has snapshots, only the current state of the machine will be 63 exported. The disk images in the export will have a 64 <i>flattened</i> state identical to the current 65 state of the virtual machine. 66 </p> 38 <p>OVF cannot describe snapshots that were taken for a virtual machine. As a result, when you export a virtual 39 machine that has snapshots, only the current state of the machine will be exported. The disk images in the 40 export will have a <i>flattened</i> state identical to the current state of the virtual machine. </p> 67 41 </note> 68 42 </body>
Note:
See TracChangeset
for help on using the changeset viewer.
