| 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-import-appliance">
|
|---|
| 4 | <title>Importing an Appliance in OVF Format</title>
|
|---|
| 5 |
|
|---|
| 6 | <body>
|
|---|
| 7 | <p>The following steps show how to import an appliance in OVF format. </p>
|
|---|
| 8 | <ol>
|
|---|
| 9 | <li>
|
|---|
| 10 | <p>Double-click the OVF or OVA file. </p>
|
|---|
| 11 | <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> creates file type associations automatically for any
|
|---|
| 12 | OVF and OVA files on your host OS. </p>
|
|---|
| 13 | <p>The <b outputclass="bold">Appliance Settings</b> page of the <b outputclass="bold">Import Virtual
|
|---|
| 14 | Appliance</b> wizard is shown. This page shows the VMs described in the OVF or OVA file and enables you to
|
|---|
| 15 | change the VM settings. </p>
|
|---|
| 16 | </li>
|
|---|
| 17 | <li>
|
|---|
| 18 | <p>By default, membership of VM groups is preserved on import for VMs that were initially exported from <ph
|
|---|
| 19 | conkeyref="vbox-conkeyref-phrases/product-name"/>. You can change this behavior by using the <b
|
|---|
| 20 | outputclass="bold">Primary Group</b> setting for the VM. </p>
|
|---|
| 21 | <p>The following global settings apply to all of the VMs that you import: </p>
|
|---|
| 22 | <ul>
|
|---|
| 23 | <li>
|
|---|
| 24 | <p><b outputclass="bold">Base Folder:</b> Specifies
|
|---|
| 25 | the directory on the host in which to store the imported
|
|---|
| 26 | VMs.
|
|---|
| 27 | </p>
|
|---|
| 28 | <p>If an appliance has multiple VMs, you can specify a different directory for each VM by editing the <b
|
|---|
| 29 | outputclass="bold">Base Folder</b> setting for the VM. </p>
|
|---|
| 30 | </li>
|
|---|
| 31 | <li>
|
|---|
| 32 | <p><b outputclass="bold">MAC Address Policy:</b>
|
|---|
| 33 | Reinitializes the MAC addresses of network cards in your
|
|---|
| 34 | VMs prior to import, by default. You can override the
|
|---|
| 35 | default behavior and preserve the MAC addresses on
|
|---|
| 36 | import.
|
|---|
| 37 | </p>
|
|---|
| 38 | </li>
|
|---|
| 39 | <li>
|
|---|
| 40 | <p><b outputclass="bold">Import Hard Drives as
|
|---|
| 41 | VDI:</b> Imports hard drives in the VDI format
|
|---|
| 42 | rather than in the default VMDK format.
|
|---|
| 43 | </p>
|
|---|
| 44 | </li>
|
|---|
| 45 | </ul>
|
|---|
| 46 | </li>
|
|---|
| 47 | <li>
|
|---|
| 48 | <p>Click <b outputclass="bold">Finish</b> to import the appliance. </p>
|
|---|
| 49 | <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> copies the disk images and creates local VMs with the
|
|---|
| 50 | settings described on the <b outputclass="bold">Appliance Settings</b> page. The imported VMs are shown in the
|
|---|
| 51 | list of VMs in VirtualBox Manager. </p>
|
|---|
| 52 | <p>Because disk images are large, the VMDK images that are included with virtual appliances are shipped in a
|
|---|
| 53 | compressed format that cannot be used directly by VMs. So, the images are first unpacked and copied, which
|
|---|
| 54 | might take several minutes. </p>
|
|---|
| 55 | </li>
|
|---|
| 56 | </ol>
|
|---|
| 57 | <p>You can use the <userinput>VBoxManage import</userinput> command to import an appliance. See <xref href="../cli_topics/vboxmanage-import.dita"/>.</p>
|
|---|
| 58 | </body>
|
|---|
| 59 |
|
|---|
| 60 | </topic>
|
|---|
