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="create-vm-wizard-virtual-hard-disk">
|
---|
4 | <title>Specify a Virtual Hard Disk</title>
|
---|
5 |
|
---|
6 | <body>
|
---|
7 | <p>There are many ways in which <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can
|
---|
8 | provide hard disk space to a VM, see <xref href="storage.dita#storage"/>. </p>
|
---|
9 | <p>The most common way is to use a virtual hard disk. This is a large image file on your
|
---|
10 | physical hard disk, whose contents <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
|
---|
11 | presents to your VM as if it were a complete hard disk. You can copy this file to another
|
---|
12 | host, and use it with another <ph conkeyref="vbox-conkeyref-phrases/product-name"/> VM. </p>
|
---|
13 | <p>To prevent your physical hard disk on the host OS from filling up, <ph
|
---|
14 | conkeyref="vbox-conkeyref-phrases/product-name"/> limits the size of the image file. But the
|
---|
15 | image file must be large enough to hold the contents of the guest OS and the applications you
|
---|
16 | want to install. For a Windows or Linux guest, you will probably need several gigabytes for
|
---|
17 | any serious use. The size limit of the image file can be changed later, see <xref
|
---|
18 | href="vboxmanage-modifymedium.dita"/>. </p>
|
---|
19 | <p>
|
---|
20 | <note id="note_vc4_gjs_pbc">
|
---|
21 | <p>If you choose <b outputclass="bold">Do Not Add a Virtual Hard Disk</b> at this stage you
|
---|
22 | will need to attach a hard disk using VirtualBox Manager or VBoxManage commands before you
|
---|
23 | can install a guest operating system. </p>
|
---|
24 | </note>
|
---|
25 | </p>
|
---|
26 | <section id="section_wql_21r_pbc">
|
---|
27 | <title>Create a Virtual Hard Disk</title>
|
---|
28 | </section>
|
---|
29 | <p>Follow these steps to create a virtual hard disk to use with this VM. To prevent your
|
---|
30 | physical hard disk on the host OS from filling up, <ph
|
---|
31 | conkeyref="vbox-conkeyref-phrases/product-name"/> limits the size of the image file. But the
|
---|
32 | image file must be large enough to hold the contents of the guest OS and the applications you
|
---|
33 | want to install. For a Windows or Linux guest, you will probably need several gigabytes for
|
---|
34 | any serious use. The limit of the image file size can be changed later, see <xref
|
---|
35 | href="vboxmanage-modifymedium.dita"/>. <ol id="ol_z2h_q5q_pbc">
|
---|
36 | <li>
|
---|
37 | <p>Select <b outputclass="bold">Create a Virtual Hard Disk Now</b>. This creates a new
|
---|
38 | empty virtual hard disk image, located in the VM's machine folder. </p>
|
---|
39 | </li>
|
---|
40 | <li>
|
---|
41 | <p> Enter the following settings: </p>
|
---|
42 | <ul id="ul_i3n_y1r_pbc">
|
---|
43 | <li>
|
---|
44 | <p><b outputclass="bold">Disk Size</b>. Use the slider to select a maximum size for
|
---|
45 | the hard disk in the new VM. </p>
|
---|
46 | </li>
|
---|
47 | <li>
|
---|
48 | <p><b outputclass="bold">Pre-Allocate Full Size.</b> This setting determines the type
|
---|
49 | of image file used for the disk image. Select this setting to use a <i>fixed-size
|
---|
50 | file</i> for the disk image. Otherwise, <ph
|
---|
51 | conkeyref="vbox-conkeyref-phrases/product-name"/> will use a <i>dynamically
|
---|
52 | allocated file</i> for the disk image. </p>
|
---|
53 | <p>The different types of image file behave as follows: </p>
|
---|
54 | <ul id="ul_j3n_y1r_pbc">
|
---|
55 | <li>
|
---|
56 | <p><b outputclass="bold">Dynamically allocated file.</b> This type of image file
|
---|
57 | only grows in size when the guest actually stores data on its virtual hard disk.
|
---|
58 | Therefore, this file is small initially. As the drive is filled with data, the
|
---|
59 | file grows to the specified size. </p>
|
---|
60 | </li>
|
---|
61 | <li>
|
---|
62 | <p><b outputclass="bold">Fixed-size file.</b> This type of image file immediately
|
---|
63 | occupies the file specified, even if only a fraction of that virtual hard disk
|
---|
64 | space is actually in use. While occupying much more space, a fixed-size file
|
---|
65 | incurs less overhead and is therefore slightly faster than a dynamically
|
---|
66 | allocated file. </p>
|
---|
67 | </li>
|
---|
68 | </ul>
|
---|
69 | <p> For more details about the differences, see <xref
|
---|
70 | href="vdidetails.dita#vdidetails"/>. </p>
|
---|
71 | </li>
|
---|
72 | </ul>
|
---|
73 | </li>
|
---|
74 | </ol></p>
|
---|
75 | <section id="section_bdq_h1r_pbc">
|
---|
76 | <title>Use an Existing Virtual Hard Disk</title>
|
---|
77 | </section>
|
---|
78 | <p>Follow these steps to use a virtual hard disk that already exists on the host. Ensure the
|
---|
79 | image file is in a suitable location (usually the machine folder) and not in use by other
|
---|
80 | VMs.<ol id="ol_txk_str_pbc">
|
---|
81 | <li>
|
---|
82 | <p>Select <b outputclass="bold">Use an Existing Virtual Hard Disk File</b>
|
---|
83 | </p>
|
---|
84 | </li>
|
---|
85 | <li>
|
---|
86 | <p>Select the image file to use with the new VM, and then click <b outputclass="bold"
|
---|
87 | >Add</b>. </p>
|
---|
88 | </li>
|
---|
89 | </ol></p>
|
---|
90 | <p> </p>
|
---|
91 | </body>
|
---|
92 |
|
---|
93 | </topic>
|
---|