| 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>
|
|---|
| 8 | The following steps show how to import an appliance in OVF
|
|---|
| 9 | format.
|
|---|
| 10 | </p>
|
|---|
| 11 | <ol>
|
|---|
| 12 | <li>
|
|---|
| 13 | <p> Double-click the OVF or OVA file. </p>
|
|---|
| 14 | <p>
|
|---|
| 15 | <ph conkeyref="vbox-conkeyref-phrases/product-name"/> creates file type associations automatically
|
|---|
| 16 | for any OVF and OVA files on your host OS.
|
|---|
| 17 | </p>
|
|---|
| 18 | <p>
|
|---|
| 19 | The <b outputclass="bold">Appliance Settings</b> page
|
|---|
| 20 | of the <b outputclass="bold">Import Virtual
|
|---|
| 21 | Appliance</b> wizard is shown.
|
|---|
| 22 | </p>
|
|---|
| 23 | <fig id="fig-import-appliance">
|
|---|
| 24 | <title>Import Virtual Appliance Wizard: Appliance Settings</title>
|
|---|
| 25 | <xref href="images/ovf-import.png" format="png" platform="htmlhelp">
|
|---|
| 26 | <image href="images/ovf-import.png" width="12cm" placement="break">
|
|---|
| 27 | <alt>Import Virtual Appliance Wizard: Appliance Settings</alt>
|
|---|
| 28 | </image>
|
|---|
| 29 | </xref>
|
|---|
| 30 | <image platform="ohc" href="images/ovf-import.png" width="12cm" placement="break">
|
|---|
| 31 | <alt>Import Virtual Appliance Wizard: Appliance Settings</alt>
|
|---|
| 32 | </image>
|
|---|
| 33 | </fig>
|
|---|
| 34 | </li>
|
|---|
| 35 | <li>
|
|---|
| 36 | <p>
|
|---|
| 37 | The <b outputclass="bold">Appliance Settings</b> page
|
|---|
| 38 | shows the VMs described in the OVF or OVA file and enables
|
|---|
| 39 | you to change the VM settings.
|
|---|
| 40 | </p>
|
|---|
| 41 | <p>
|
|---|
| 42 | By default, membership of VM groups is preserved on import
|
|---|
| 43 | for VMs that were initially exported from <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
|
|---|
| 44 | You can change this behavior by using the
|
|---|
| 45 | <b outputclass="bold">Primary Group</b> setting for
|
|---|
| 46 | the VM.
|
|---|
| 47 | </p>
|
|---|
| 48 | <p>
|
|---|
| 49 | The following global settings apply to all of the VMs that
|
|---|
| 50 | you import:
|
|---|
| 51 | </p>
|
|---|
| 52 | <ul>
|
|---|
| 53 | <li>
|
|---|
| 54 | <p><b outputclass="bold">Base Folder:</b> Specifies
|
|---|
| 55 | the directory on the host in which to store the imported
|
|---|
| 56 | VMs.
|
|---|
| 57 | </p>
|
|---|
| 58 | <p>
|
|---|
| 59 | If an appliance has multiple VMs, you can specify a
|
|---|
| 60 | different directory for each VM by editing the
|
|---|
| 61 | <b outputclass="bold">Base Folder</b> setting for
|
|---|
| 62 | the VM.
|
|---|
| 63 | </p>
|
|---|
| 64 | </li>
|
|---|
| 65 | <li>
|
|---|
| 66 | <p><b outputclass="bold">MAC Address Policy:</b>
|
|---|
| 67 | Reinitializes the MAC addresses of network cards in your
|
|---|
| 68 | VMs prior to import, by default. You can override the
|
|---|
| 69 | default behavior and preserve the MAC addresses on
|
|---|
| 70 | import.
|
|---|
| 71 | </p>
|
|---|
| 72 | </li>
|
|---|
| 73 | <li>
|
|---|
| 74 | <p><b outputclass="bold">Import Hard Drives as
|
|---|
| 75 | VDI:</b> Imports hard drives in the VDI format
|
|---|
| 76 | rather than in the default VMDK format.
|
|---|
| 77 | </p>
|
|---|
| 78 | </li>
|
|---|
| 79 | </ul>
|
|---|
| 80 | </li>
|
|---|
| 81 | <li>
|
|---|
| 82 | <p>
|
|---|
| 83 | Click <b outputclass="bold">Finish</b> to import the
|
|---|
| 84 | appliance.
|
|---|
| 85 | </p>
|
|---|
| 86 | <p>
|
|---|
| 87 | <ph conkeyref="vbox-conkeyref-phrases/product-name"/> copies the disk images and creates local VMs
|
|---|
| 88 | with the settings described on the
|
|---|
| 89 | <b outputclass="bold">Appliance Settings</b> page.
|
|---|
| 90 | The imported VMs are shown in the list of VMs in VirtualBox
|
|---|
| 91 | Manager.
|
|---|
| 92 | </p>
|
|---|
| 93 | <p>
|
|---|
| 94 | Because disk images are large, the VMDK images that are
|
|---|
| 95 | included with virtual appliances are shipped in a compressed
|
|---|
| 96 | format that cannot be used directly by VMs. So, the images
|
|---|
| 97 | are first unpacked and copied, which might take several
|
|---|
| 98 | minutes.
|
|---|
| 99 | </p>
|
|---|
| 100 | </li>
|
|---|
| 101 | </ol>
|
|---|
| 102 | <p> You can use the <userinput>VBoxManage import</userinput> command to import an appliance. See
|
|---|
| 103 | <xref href="vboxmanage-import.dita"/>. </p>
|
|---|
| 104 | </body>
|
|---|
| 105 |
|
|---|
| 106 | </topic>
|
|---|
