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