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