|
Last change
on this file was 108921, checked in by vboxsync, 4 weeks ago |
|
Docs: bugref:10705. The following commits from doc's team git repo has been applied:
6c76f3636576368d4a9963539c9d13348e208183 EFI only for Arm
85ce91f98ba4a229be6e435bea6678ca43f87b4d Changed topic IDs
81c094808cde6217550ab02b74c22d487d1a1746 Updated topic IDs and links to them
50717ec1eaea65d137bde7eb168b519a6b1d9966 Updated topic IDs
75466c5935ec603a2be966669f232bd088b3f287 Updated cloud intro
713b0c03d33098af0158ae0615a4f61370cabdef Updated comments
|
-
Property svn:eol-style
set to
native
-
Property svn:keywords
set to
Author Date Id Revision
|
|
File size:
2.2 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="tk_create-vm-hardware">
|
|---|
| 4 | <title>Specify Virtual Hardware</title>
|
|---|
| 5 | <body>
|
|---|
| 6 | <ol id="ol_ndb_dbx_4bc">
|
|---|
| 7 | <li>
|
|---|
| 8 | <p>Based on the OS you have chosen, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> suggests a suitable default size for <uicontrol>Base Memory</uicontrol>. This is the amount of RAM that <ph conkeyref="vbox-conkeyref-phrases/product-name"/> should allocate to the virtual machine (VM) every time it is started. The guest OS will report this size as the VM's installed RAM. </p>
|
|---|
| 9 | <note type="caution" id="note_pjs_x1x_4bc">
|
|---|
| 10 | <p>Choose this setting carefully. The memory you give to the VM will not be available to your host OS while the VM is running.</p>
|
|---|
| 11 | </note>
|
|---|
| 12 | <p>Do not specify more than you can spare, whilst ensuring you allocate enough for your guest OS and applications to run properly. For example, if your host machine has 4 GB of RAM and you enter 2048 MB as the base memory for a VM, you will have 2 GB left for all the other software on your host while that VM is running.</p>
|
|---|
| 13 | <p>A guest OS may require at least 1 or 2 GB of memory to install and boot up. If you intend to run more than one VM at a time, plan accordingly. A VM will not start if it does not have enough RAM to boot.</p>
|
|---|
| 14 | <p>Always ensure that the host OS has enough RAM remaining. If insufficient RAM remains, the system might excessively swap memory to the hard disk, which will effectively bring the host system to a standstill.</p>
|
|---|
| 15 | </li>
|
|---|
| 16 | <li>
|
|---|
| 17 | <p>For <uicontrol>Processors</uicontrol>, select the number of virtual processors to assign to the VM. Do not assign more than half of the total processor threads from the host machine.</p>
|
|---|
| 18 | </li>
|
|---|
| 19 | <li><p>Choose the <uicontrol>Disk Size</uicontrol> for a new, dynamically allocated, virtual hard disk image to be created in the VM folder.</p> For other options when allocating virtual storage, see <xref href="storage.dita"/>.</li>
|
|---|
| 20 | <li>
|
|---|
| 21 | <p>Select <uicontrol>Use EFI</uicontrol> to boot the guest OS using Extended Firmware Interface (EFI).</p>
|
|---|
| 22 | </li>
|
|---|
| 23 | </ol>
|
|---|
| 24 | </body>
|
|---|
| 25 | </topic>
|
|---|
Note:
See
TracBrowser
for help on using the repository browser.
