| 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-processor">
|
|---|
| 4 | <title>Processor Tab</title>
|
|---|
| 5 |
|
|---|
| 6 | <body>
|
|---|
| 7 | <p>On the <b outputclass="bold">Processor</b> tab, you can configure settings for the CPU used by the virtual
|
|---|
| 8 | machine. </p>
|
|---|
| 9 | <ul>
|
|---|
| 10 | <li>
|
|---|
| 11 | <p><b outputclass="bold">Processor(s):</b> Sets the
|
|---|
| 12 | number of virtual CPU cores the guest OSes can see.
|
|---|
| 13 | <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports symmetrical multiprocessing (SMP)
|
|---|
| 14 | and can present up to 32 virtual CPU cores to each virtual
|
|---|
| 15 | machine.
|
|---|
| 16 | </p>
|
|---|
| 17 | <p>
|
|---|
| 18 | You should not configure virtual machines to use more CPU
|
|---|
| 19 | cores than are available physically. This includes real
|
|---|
| 20 | cores, with no hyperthreads.
|
|---|
| 21 | </p>
|
|---|
| 22 | </li>
|
|---|
| 23 | <li>
|
|---|
| 24 | <p><b outputclass="bold">Execution Cap:</b> Configures
|
|---|
| 25 | the CPU execution cap. This limits the amount of time a host
|
|---|
| 26 | CPU spends to emulate a virtual CPU. The default setting is
|
|---|
| 27 | 100%, meaning that there is no limitation. A setting of 50%
|
|---|
| 28 | implies a single virtual CPU can use up to 50% of a single
|
|---|
| 29 | host CPU. Note that limiting the execution time of the
|
|---|
| 30 | virtual CPUs may cause guest timing problems.
|
|---|
| 31 | </p>
|
|---|
| 32 | <p>
|
|---|
| 33 | A warning is displayed at the bottom of the Processor tab if
|
|---|
| 34 | an Execution Cap setting is made that may affect system
|
|---|
| 35 | performance.
|
|---|
| 36 | </p>
|
|---|
| 37 | </li>
|
|---|
| 38 | <li>
|
|---|
| 39 | <p><b outputclass="bold">Enable PAE/NX (Can't be changed on VMs with an Arm architecture):</b> Determines whether the PAE and NX capabilities of the host CPU will be exposed to the virtual machine. </p>
|
|---|
| 40 | <p>
|
|---|
| 41 | PAE stands for Physical Address Extension. Normally, if
|
|---|
| 42 | enabled and supported by the OS, then even a 32-bit x86 CPU
|
|---|
| 43 | can access more than 4 GB of RAM. This is made possible by
|
|---|
| 44 | adding another 4 bits to memory addresses, so that with 36
|
|---|
| 45 | bits, up to 64 GB can be addressed. Some OSes, such as
|
|---|
| 46 | Ubuntu Server, require PAE support from the CPU and cannot
|
|---|
| 47 | be run in a virtual machine without it.
|
|---|
| 48 | </p>
|
|---|
| 49 | </li>
|
|---|
| 50 | <li>
|
|---|
| 51 | <p><b outputclass="bold">Enable Nested VT-x/AMD-V (Can't be changed on VMs with an Arm architecture)</b>: Enables nested virtualization, with passthrough of hardware virtualization functions to the guest VM. </p>
|
|---|
| 52 | </li>
|
|---|
| 53 | </ul>
|
|---|
| 54 | <p>With virtual machines running modern server OSes, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> also
|
|---|
| 55 | supports CPU hot-plugging. For details, see <xref href="cpuhotplug.dita">CPU Hot-Plugging</xref>. </p>
|
|---|
| 56 | </body>
|
|---|
| 57 |
|
|---|
| 58 | </topic>
|
|---|
