VirtualBox

source: vbox/trunk/doc/manual/en_US/dita/topics/settings-motherboard.dita

最後變更 在這個檔案是 108297,由 vboxsync 提交於 4 週 前

Docs: bugref:10705. The following commits from doc's team git repo has been applied:

38ede4e3c915bbab9000b1b990e187daa07b4f61 Created 7.2 books from the 7.1 content with new part numbers, variables and removed non-7.2 content.
0951cfa5daf57ec2a81e36d335f14d8b4f2acd87 Merge branch 'Finalise_seamless_windows' into 'main'
b9e418eb08b28c6353e3f4534c7e360269cf5eef Included Klaus' feedback on known issues, moved some.
373130ebe466a21f4271e2ac36f11709c3697093 Initial edits to troubleshooting topics
a7459a9a24b73b4d268a751fba85e595ad6f35db Restructured and updated troubleshooting section
e3f67c800044e585a4428a4fc76016980269301b Added comments for future work
dcc46e566f3d269e5994d83cc5421532421fa639 Initial restructuring to move topics into suitable sections
e7b6f99bf86526813fcbe96903cf0c2652952eb0 removed Guest Control known issue. Info now in CLI topics
0209a6a155f460eaba79bcf0d0f34d8460413868 Reworded clipboard intro to be clear it requires GUI, made config a separate chapter
94f883f2b38dc281e759878880280370aa517d5c Included feedback from Brent on troubleshooting
ac1c0c919eeb58b1db478ca66e825ea89eb7a1a8 Removed preface, consolidated intro topics
7117e423ecdc1841b2bbca1aafda1c43ae38f7ea More restructuring and removing duplication
c8728eee82bd4081ab6f0500b32068c8f6749bc2 Updated intro and more restructuring
25389ab0df09df59f8f5f517f15590a917bb66a1 Added link to support and licensing
981ba048798bf7985f2c230fe97172d587e25fd6 7.2 updates for 3d acceleration
e95113d1da7ccf299642cd3368804e319e2bf3ca Updated diagram in intro, and filename
5c4555249e12738e55e9b8a0710f83ee7d4a9e61 New filenames, ids for intro
abf8d5092aea7f1fd4e9b7dbab578d615579eb4e Updated diagram to higher res

  • 屬性 svn:eol-style 設為 native
  • 屬性 svn:keywords 設為 Author Date Id Revision
檔案大小: 7.4 KB
 
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 OSs 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"/>. However, no ACPI information, such as battery status or power source, is reported to Oracle Solaris guests.</p>
95 <p>ACPI can only be turned off using the command line. See <xref href="../cli_topics/vboxmanage-modifyvm.dita"/>.</p>
96 <note>
97 <p>All Windows OSes install different kernels, depending on whether ACPI is available. This means that ACPI
98 <i>must not be turned off</i> after installation of a Windows guest OS. However, turning it on after
99 installation will have no effect. </p>
100 </note>
101 </body>
102
103</topic>
注意: 瀏覽 TracBrowser 來幫助您使用儲存庫瀏覽器

© 2025 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette