| 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="settings-motherboard">
|
|---|
| 4 | <title>Motherboard Tab</title>
|
|---|
| 5 |
|
|---|
| 6 | <body>
|
|---|
| 7 | <p>
|
|---|
| 8 | On the <b outputclass="bold">Motherboard</b> tab, you can
|
|---|
| 9 | configure virtual hardware that would normally be on the
|
|---|
| 10 | motherboard of a real computer.
|
|---|
| 11 | </p>
|
|---|
| 12 | <ul>
|
|---|
| 13 | <li>
|
|---|
| 14 | <p><b outputclass="bold">Base Memory:</b> Sets the
|
|---|
| 15 | amount of RAM that is allocated and given to the VM when it
|
|---|
| 16 | is running. The specified amount of memory will be requested
|
|---|
| 17 | from the host OS, so it must be available or made available
|
|---|
| 18 | as free memory on the host when attempting to start the VM
|
|---|
| 19 | and will not be available to the host while the VM is
|
|---|
| 20 | running. This is the same setting that was specified in the
|
|---|
| 21 | <b outputclass="bold">New Virtual Machine</b> wizard,
|
|---|
| 22 | as described in <xref href="create-vm-wizard.dita#create-vm-wizard"/>.
|
|---|
| 23 | </p>
|
|---|
| 24 | <p>
|
|---|
| 25 | Generally, it is possible to change the memory size after
|
|---|
| 26 | installing the guest OS. But you must not reduce the memory
|
|---|
| 27 | to an amount where the OS would no longer boot.
|
|---|
| 28 | </p>
|
|---|
| 29 | </li>
|
|---|
| 30 | <li>
|
|---|
| 31 | <p><b outputclass="bold">Boot Order:</b> Determines the
|
|---|
| 32 | order in which the guest OS will attempt to boot from the
|
|---|
| 33 | various virtual boot devices. Analogous to a real PC's BIOS
|
|---|
| 34 | setting, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can tell a guest OS to start from
|
|---|
| 35 | the virtual floppy, the virtual CD/DVD drive, the virtual
|
|---|
| 36 | hard drive (each of these as defined by the other VM
|
|---|
| 37 | settings), the network, or none of these.
|
|---|
| 38 | </p>
|
|---|
| 39 | <p>
|
|---|
| 40 | If you select <b outputclass="bold">Network</b>, the VM will attempt to boot from a
|
|---|
| 41 | network using the PXE mechanism. This needs to be configured in detail on the command
|
|---|
| 42 | line. See <xref href="vboxmanage-modifyvm.dita"/>.
|
|---|
| 43 | </p>
|
|---|
| 44 | </li>
|
|---|
| 45 | <li>
|
|---|
| 46 | <p><b outputclass="bold">Chipset:</b> You can select
|
|---|
| 47 | which chipset will be presented to the virtual machine.
|
|---|
| 48 | PIIX3 is the default chipset for most guests. For some guest
|
|---|
| 49 | OSes such as Mac OS X, the PIIX3 chipset is not well
|
|---|
| 50 | supported. As a result, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports an emulation
|
|---|
| 51 | of the ICH9 chipset, which supports PCI express, three PCI
|
|---|
| 52 | buses, PCI-to-PCI bridges and Message Signaled Interrupts
|
|---|
| 53 | (MSI). This enables modern OSes to address more PCI devices
|
|---|
| 54 | and no longer requires IRQ sharing. Using the ICH9 chipset
|
|---|
| 55 | it is also possible to configure up to 36 network cards,
|
|---|
| 56 | compared to a maximum of eight network adapters with PIIX3.
|
|---|
| 57 | Note that ICH9 support is experimental and not recommended
|
|---|
| 58 | for guest OSes which do not require it.
|
|---|
| 59 | </p>
|
|---|
| 60 | <!-- 7.1: Any chipset options for Arm?-->
|
|---|
| 61 | </li>
|
|---|
| 62 | <li>
|
|---|
| 63 | <p><b outputclass="bold">TPM:</b> Enables support for a
|
|---|
| 64 | Trusted Platform Module (TPM) security processor. Choose
|
|---|
| 65 | from the supported TPM versions.
|
|---|
| 66 | </p>
|
|---|
| 67 | </li>
|
|---|
| 68 | <li>
|
|---|
| 69 | <p><b outputclass="bold">Pointing Device:</b> The
|
|---|
| 70 | default virtual pointing device for some guest OSes is the
|
|---|
| 71 | traditional PS/2 mouse. If set to <b outputclass="bold">USB
|
|---|
| 72 | Tablet</b>, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> reports to the virtual
|
|---|
| 73 | machine that a USB tablet device is present and communicates
|
|---|
| 74 | mouse events to the virtual machine through this device.
|
|---|
| 75 | Another setting is <b outputclass="bold">USB Multi-Touch
|
|---|
| 76 | Tablet</b>, which is suitable for guests running
|
|---|
| 77 | Windows 8 or later.
|
|---|
| 78 | </p>
|
|---|
| 79 | <p>
|
|---|
| 80 | Using the virtual USB tablet has the advantage that
|
|---|
| 81 | movements are reported in absolute coordinates, instead of
|
|---|
| 82 | as relative position changes. This enables <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to
|
|---|
| 83 | translate mouse events over the VM window into tablet events
|
|---|
| 84 | without having to "capture" the mouse in the guest as
|
|---|
| 85 | described in <xref href="keyb_mouse_normal.dita#keyb_mouse_normal"/>. This
|
|---|
| 86 | makes using the VM less tedious even if Guest Additions are
|
|---|
| 87 | not installed.
|
|---|
| 88 | </p>
|
|---|
| 89 | </li>
|
|---|
| 90 | <li>
|
|---|
| 91 | <p><b outputclass="bold">Enable I/O APIC:</b> Advanced
|
|---|
| 92 | Programmable Interrupt Controllers (APICs) are an x86
|
|---|
| 93 | hardware feature that have replaced Programmable Interrupt
|
|---|
| 94 | Controllers (PICs). With an I/O APIC, OSes can use more than
|
|---|
| 95 | 16 interrupt requests (IRQs) and therefore avoid IRQ sharing
|
|---|
| 96 | for improved reliability.
|
|---|
| 97 | </p>
|
|---|
| 98 | <note>
|
|---|
| 99 | <p>
|
|---|
| 100 | Enabling the I/O APIC is <i>required</i>,
|
|---|
| 101 | especially for 64-bit Windows guest OSes. It is also
|
|---|
| 102 | required if you want to use more than one virtual CPU in a
|
|---|
| 103 | virtual machine.
|
|---|
| 104 | </p>
|
|---|
| 105 | </note>
|
|---|
| 106 | <p>
|
|---|
| 107 | However, software support for I/O APICs has been unreliable
|
|---|
| 108 | with some OSes other than Windows. Also, the use of an I/O
|
|---|
| 109 | APIC slightly increases the overhead of virtualization and
|
|---|
| 110 | therefore slows down the guest OS a little.
|
|---|
| 111 | </p>
|
|---|
| 112 | <note type="attention">
|
|---|
| 113 | <p>
|
|---|
| 114 | All Windows OSes install different kernels, depending on
|
|---|
| 115 | whether an I/O APIC is available. As with ACPI, the I/O
|
|---|
| 116 | APIC therefore <i>must not be turned off after
|
|---|
| 117 | installation</i> of a Windows guest OS. Turning it
|
|---|
| 118 | on after installation will have no effect however.
|
|---|
| 119 | </p>
|
|---|
| 120 | </note>
|
|---|
| 121 | </li>
|
|---|
| 122 | <li>
|
|---|
| 123 | <p><b outputclass="bold">Hardware Clock in UTC Time:</b>
|
|---|
| 124 | If selected, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will report the system time in
|
|---|
| 125 | UTC format to the guest instead of the local (host) time.
|
|---|
| 126 | This affects how the virtual real-time clock (RTC) operates
|
|---|
| 127 | and may be useful for UNIX-like guest OSes, which typically
|
|---|
| 128 | expect the hardware clock to be set to UTC.
|
|---|
| 129 | </p>
|
|---|
| 130 | </li>
|
|---|
| 131 | <li>
|
|---|
| 132 | <p><b outputclass="bold">Enable EFI:</b> Enables
|
|---|
| 133 | Extensible Firmware Interface (EFI), which replaces the
|
|---|
| 134 | legacy BIOS and may be useful for certain advanced use
|
|---|
| 135 | cases. See <xref href="efi.dita#efi"/>.
|
|---|
| 136 | </p>
|
|---|
| 137 | </li>
|
|---|
| 138 | <li>
|
|---|
| 139 | <p><b outputclass="bold">Enable Secure Boot:</b> Enables
|
|---|
| 140 | Secure Boot, to provide a secure environment for starting
|
|---|
| 141 | the guest OS.
|
|---|
| 142 | </p>
|
|---|
| 143 | </li>
|
|---|
| 144 | </ul>
|
|---|
| 145 | <p>
|
|---|
| 146 | In addition, you can turn off the <b outputclass="bold">Advanced
|
|---|
| 147 | Configuration and Power Interface (ACPI)</b> which
|
|---|
| 148 | <ph conkeyref="vbox-conkeyref-phrases/product-name"/> presents to the guest OS by default.
|
|---|
| 149 | </p>
|
|---|
| 150 | <p>
|
|---|
| 151 | ACPI is the current industry standard to allow OSes to recognize hardware, configure
|
|---|
| 152 | motherboards and other devices and manage power. As most computers contain this feature and
|
|---|
| 153 | Windows and Linux support ACPI, it is also enabled by default in <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. ACPI
|
|---|
| 154 | can only be turned off using the command line. See <xref href="vboxmanage-modifyvm.dita"/>.
|
|---|
| 155 | </p>
|
|---|
| 156 | <note type="attention">
|
|---|
| 157 | <p>
|
|---|
| 158 | All Windows OSes install different kernels, depending on
|
|---|
| 159 | whether ACPI is available. This means that ACPI <i>must
|
|---|
| 160 | not be turned off</i> after installation of a Windows
|
|---|
| 161 | guest OS. However, turning it on after installation will have
|
|---|
| 162 | no effect.
|
|---|
| 163 | </p>
|
|---|
| 164 | </note>
|
|---|
| 165 | </body>
|
|---|
| 166 |
|
|---|
| 167 | </topic>
|
|---|
