VirtualBox

source: vbox/trunk/doc/manual/en_US/dita/topics/ovf-import-appliance.dita@ 98549

Last change on this file since 98549 was 98549, checked in by vboxsync, 2 years ago

Docs: bugref:10302. Uploading .dita user manual files we received from the doc team on 25th Jan.

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

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette