Xen Hypervisor Command Line Options

This document covers the command line options which the Xen Hypervisor.

Types of parameter

Most parameters take the form option=value. Different options on the command line should be space delimited. All options are case sensitive, as are all values unless explicitly noted.

Boolean (<boolean>)

All boolean option may be explicitly enabled using a value of

yes, on, true, enable or 1

They may be explicitly disabled using a value of

no, off, false, disable or 0

In addition, a boolean option may be enabled by simply stating its name, and may be disabled by prefixing its name with no-.


Enable noreboot mode


Disable x2apic support (if present)


Enable synchronous console mode


Explicitly specifying any value other than those listed above is undefined, as is stacking a no- prefix with an explicit value.

Integer (<integer>)

An integer parameter will default to decimal and may be prefixed with a - for negative numbers. Alternatively, a hexadecimal number may be used by prefixing the number with 0x, or an octal number may be used if a leading 0 is present.

Providing a string which does not validly convert to an integer is undefined.

Size (<size>)

A size parameter may be any integer, with a single size suffix

Without a size suffix, the default will be kilo. Providing a suffix other than those listed above is undefined.


Many parameters are more complicated and require more intricate configuration. The detailed description of each individual parameter specify which values are valid.


Some options take a comma separated list of values.


Some parameters act as combinations of the above, most commonly a mix of Boolean and String. These are noted in the relevant sections.

Parameter details


= force | ht | noirq | <boolean>

String, or Boolean to disable.

The acpi option is used to control a set of four related boolean flags; acpi_force, acpi_ht, acpi_noirq and acpi_disabled.

By default, Xen will scan the DMI data and blacklist certain systems which are known to have broken ACPI setups. Providing acpi=force will cause Xen to ignore the blacklist and attempt to use all ACPI features.

Using acpi=ht causes Xen to parse the ACPI tables enough to enumerate all CPUs, but will not use other ACPI features. This is not common, and only has an effect if your system is blacklisted.

The acpi=noirq option causes Xen to not parse the ACPI MADT table looking for IO-APIC entries. This is also not common, and any system which requires this option to function should be blacklisted. Additionally, this will not prevent Xen from finding IO-APIC entries from the MP tables.

Finally, any of the boolean false options can be used to disable ACPI usage entirely.

Because responsibility for ACPI processing is shared between Xen and the domain 0 kernel this option is automatically propagated to the domain 0 command line


= <integer>

Specify which ACPI MADT table to parse for APIC information, if more than one is present.


= <boolean>

Default: false

Enforce checking that P-state transitions by the ACPI cpufreq driver actually result in the nominated frequency to be established. A warning message will be logged if that isn't the case.


= <boolean>

Instruct Xen to ignore timer-interrupt override.


= s3_bios | s3_mode

s3_bios instructs Xen to invoke video BIOS initialization during S3 resume.

s3_mode instructs Xen to set up the boot time (option vga=) video mode during S3 resume.


= <boolean>

Default: true

Permit Xen to use superpages when performing memory management.


= bigsmp | default

Override Xen's logic for choosing the APIC driver. By default, if there are more than 8 CPUs, Xen will switch to bigsmp over default.


= <boolean>

Default: false

Force boot on potentially unsafe systems. By default Xen will refuse to boot on systems with the following errata:


= verbose | debug

Increase the verbosity of the APIC code from the default value.


= <boolean>

Default: true

Permit Xen to use "Always Running APIC Timer" support on compatible hardware in combination with cpuidle. This option is only expected to be useful for developers wishing Xen to fall back to older timing methods on newer hardware.


= <boolean>

Default: true

Permits Xen to set up and use PCI Address Translation Services, which is required for PCI Passthrough.


= <size>

Default: 0 (no limit)

Specify a maximum amount of available memory, to which Xen will clamp the e820 table.


= List of [ <integer> | <integer>-<integer> ]

Specify that certain pages, or certain ranges of pages contain bad bytes and should not be used. For example, if your memory tester says that byte 0x12345678 is bad, you would place badpage=0x12345 on Xen's command line.


= <boolean>

Default: true

Scrub free RAM during boot. This is a safety feature to prevent accidentally leaking sensitive VM data into other VMs if Xen crashes and reboots.


= <size>

Default: 128M

Maximum RAM block size chunks to be scrubbed whilst holding the page heap lock and not running softirqs. Reduce this if softirqs are not being run frequently enough. Setting this to a high value may cause boot failure, particularly if the NMI watchdog is also enabled.


= <size>

If set, override Xen's calculation of the level 2 cache line size.


= pit | hpet | acpi

If set, override Xen's default choice for the platform timer.


= <boolean>

Default: false

Flag to indicate whether to probe for a CMOS Real Time Clock irrespective of ACPI indicating none to be there.


= <baud>[/<clock_hz>][,[DPS][,[<io-base>|pci|amt][,[<irq>][,[<port-bdf>][,[<bridge-bdf>]]]]]]

Both option com1 and com2 follow the same format.

A typical setup for most situations might be `com1=115200,8n1`


6e96d4b76aea66174866a39d69225c9e Specify the size of the console ring buffer.


63ec22930adbb6ca03a54e26258fce4b Specify which console(s) Xen should use. `vga` indicates that Xen should try and use the vga graphics adapter. `com1` and `com2` indicates that Xen should use serial ports 1 and 2 respectively. Optionally, these arguments may be followed by an `H` or `L`. `H` indicates that transmitted characters will have their MSB set, while received characters must have their MSB set. `L` indicates the converse; transmitted and received characters will have their MSB cleared. This allows a single port to be shared by two subsystems (e.g. console and debugger). `dbgp` indicates that Xen should use a USB debug port. `none` indicates that Xen should not use a console. This option only makes sense on its own.


0e3ffc6ab0c033ee9cc28060fb2ce697 Specify which timestamp format Xen should use for each console line. 04553f6e173bb3b1b7b54cd8ab8f9baf For compatibility with the older boolean parameter, specifying `console_timestamps` alone will enable the `date` option.


b8cb007661e45efb84961b15e19631d2 Flag to indicate whether all guest console output should be copied into the console ring buffer.


ae5e613623d77aba4ea1d848257b58ca Specify which character should be used to switch serial input between Xen and dom0. The required sequence is CTRL-<switch char> three times. The optional trailing `x` indicates that Xen should not automatically switch the console input to dom0 during boot. Any other value, including omission, causes Xen to automatically switch to the dom0 console during dom0 boot. Use `conswitch=ax` to keep the default switch character, but for xen to keep the console.


ceb49d2ff65f5598c4c58e0542fe6663 If set, force use of the performance counters for oprofile, rather than detecting available support.


5c0aa6c5706daa0b34159eb7387e7db2 Indicate where the responsibility for driving power states lies. c27f990dc8d932e01163b6180b38b6fc

cpuid_mask_cpu (AMD only)

5b99ee4309789e3916908489d3ea1cea If the other **cpuid\_mask\_{,ext\_,thermal\_,l7s0\_}e{a,b,c,d}x** options are fully set (unspecified on the command line), specify a pre-canned cpuid mask to mask the current processor down to appear as the specified processor. It is important to ensure that all hosts in a pool appear the same to guests to allow successful live migration.


7ff36d96eeb987c0ad90d49680ec5def These four command line parameters are used to specify cpuid masks to help with cpuid levelling across a pool of hosts. Setting a bit in the mask indicates that the feature should be enabled, while clearing a bit in the mask indicates that the feature should be disabled. It is important to ensure that all hosts in a pool appear the same to guests to allow successful live migration.

cpuid_mask_xsave_eax (Intel only)

7ff36d96eeb987c0ad90d49680ec5def This command line parameter is also used to specify a cpuid mask to help with cpuid levelling across a pool of hosts. See the description of the other respective options above.

cpuid_mask_{l7s0_{eax,ebx},thermal_ecx} (AMD only)

7ff36d96eeb987c0ad90d49680ec5def These three command line parameters are also used to specify cpuid masks to help with cpuid levelling across a pool of hosts. See the description of the other respective options above.






c5442ad91e7c6cb691285db26198704c Specify the maximum address to allocate certain structures, if used in combination with the `low_crashinfo` command line option.










1a4cd654bf97e968fc8fcaeb9b14d4a9 Specify the USB controller to use, either by instance number (when going over the PCI busses sequentially) or by PCI device (must be on segment 0).


c0cd3d39ffd2df3b6ff36e310b3b1bda Limits the number lines printed in Xen stack traces.


75a87558b30dbeab0cf7860812d196d1 Specify the size of the console debug trace buffer in KiB. The debug trace feature is only enabled in debugging builds of Xen.


0b57290d35d2f0e2418e894d948859d9 Specify the bit width of the DMA heap.


b2cff46a3e23f15dcbf9d3a7f9d5d4a5 Specify a list of IO ports to be excluded from dom0 access.


Either: 79afa4c21841e6613dde1d6e0ce00bbb The number of VCPUs to give to dom0. This number of VCPUs can be more than the number of PCPUs on the host. The default is the number of PCPUs. Or: c7932ddf11549531d574b735ab73a2c9 Gives dom0 a number of VCPUs equal to the number of PCPUs, but always at least `` and no more than ``. Using `` may give more VCPUs than PCPUs. `` or `` may be omitted and the defaults of 1 and unlimited respectively are used instead. For example, with `dom0_max_vcpus=4-8`:
 Number of
PCPUs | Dom0 VCPUs 2 | 4 4 | 4 6 | 6 8 | 8 10 | 8


59da965ae8293db141118a1e72e55b7d Set the amount of memory for the initial domain (dom0). If a size is positive, it represents an absolute value. If a size is negative, it is subtracted from the total available memory. e441508e8b25c04812bb8df62c616e1c If `` is not specified, the default is all the available memory minus some reserve. The reserve is 1/16 of the available memory or 128 MB (whichever is smaller). The amount of memory will be at least the minimum but never more than the maximum (i.e., `max` overrides the `min` option). If there isn't enough memory then as much as possible is allocated. `max:` also sets the maximum reservation (the maximum amount of memory dom0 can balloon up to). If this is omitted then the maximum reservation is unlimited. For example, to set dom0's initial memory allocation to 512MB but allow it to balloon up as far as 1GB use `dom0_mem=512M,max:1G` If you use this option then it is highly recommended that you disable any dom0 autoballooning feature present in your toolstack. See the _xl.conf(5)_ man page or [Xen Best Practices](http://wiki.xen.org/wiki/Xen_Best_Practices#Xen_dom0_dedicated_memory_and_preventing_dom0_memory_ballooning).




b8cb007661e45efb84961b15e19631d2 Pin dom0 vcpus to their respective pcpus


b8cb007661e45efb84961b15e19631d2 Flag that makes a 64bit dom0 boot in PVH mode. No 32bit support at present.


a5e16fbdc13974c2c340fde7a749db50 Flag that specifies if RAM should be clipped to the highest cacheable MTRR. 4ffc3270cf614fca5bb97098dbddf852


b8cb007661e45efb84961b15e19631d2 Flag that enables verbose output when processing e820 information and applying clipping.

edd (x86)

c18d3673bb014398338b5488b629b5a8 Control retrieval of Extended Disc Data (EDD) from the BIOS during boot.

edid (x86)

5d94f3812d608f2e89919e2a6a0b8266 Either force retrieval of monitor EDID information via VESA DDC, or disable it (edid=no). This option should not normally be required except for debugging purposes.


70aa8e4a5d4b5a1fcca09875a55d0617 Change the number of PIRQs available for guests. The optional first number is common for all domUs, while the optional second number (preceded by a comma) is for dom0. Changing the setting for domU has no impact on dom0 and vice versa. For example to change dom0 without changing domU, use `extra_guest_irqs=,512`






55fe1b89edeb6b392fb224555fa0f68a Specify the font size when using the VESA console driver.

force-ept (Intel)

b8cb007661e45efb84961b15e19631d2 Allow EPT to be enabled when VMX feature VM\_ENTRY\_LOAD\_GUEST\_PAT is not present. *Warning:* Due to CVE-2013-2212, VMX feature VM\_ENTRY\_LOAD\_GUEST\_PAT is by default required as a prerequisite for using EPT. If you are not using PCI Passthrough, or trust the guest administrator who would be using passthrough, then the requirement can be relaxed. This option is particularly useful for nested virtualization, to allow the L1 hypervisor to use EPT even if the L0 hypervisor does not provide VM\_ENTRY\_LOAD\_GUEST\_PAT.


be552f2bdb4c6e795e906cf8e93f8193 Specify the serial parameters for the GDB stub.


0b57290d35d2f0e2418e894d948859d9 Specify the maximum number of frames per grant table operation.


9bede1f3ebc54fa1e939c53b6843f908 Set the logging level for Xen guests. Any log message with equal more more importance will be printed. The optional `` option instructs which severities should be rate limited.


c76f4357556649e163c9b2e418ba55a3 Flag to globally enable or disable support for Hardware Assisted Paging (HAP)


c76f4357556649e163c9b2e418ba55a3 Flag to enable 1 GB host page table support for Hardware Assisted Paging (HAP).


c76f4357556649e163c9b2e418ba55a3 Flag to enable 2 MB host page table support for Hardware Assisted Paging (HAP).


f0cb0cfd8d0f644f4bc637d8bf48f094 Enable late hardware domain creation using the specified domain ID. This is intended to be used when domain 0 is a stub domain which builds a disaggregated system including a hardware domain with the specified domain ID. This option is supported only when compiled with XSM\_ENABLE=y on x86.




0b57290d35d2f0e2418e894d948859d9 The specified value is a bit mask with the individual bits having the following meaning: Bit 0 - debug level 0 (unused at present) Bit 1 - debug level 1 (Control Register logging) Bit 2 - debug level 2 (VMX logging of MSR restores when context switching) Bit 3 - debug level 3 (unused at present) Bit 4 - I/O operation logging Bit 5 - vMMU logging Bit 6 - vLAPIC general logging Bit 7 - vLAPIC timer logging Bit 8 - vLAPIC interrupt logging Bit 9 - vIOAPIC logging Bit 10 - hypercall logging Bit 11 - MSR operation logging Recognized in debug builds of the hypervisor only.


c76f4357556649e163c9b2e418ba55a3 Specify whether guests are to be given access to physical port 80 (often used for debugging purposes), to override the DMI based detection of systems known to misbehave upon accesses to that port.


3757886e26f122128736a900866d699b Specify the memory boundary past which memory will be treated as highmem (x86 debug hypervisor only).







All other sub-options are of boolean kind and can be prefixed with no- to effect the inverse meaning.

force or required

Default: false

Don't continue booting unless IOMMU support is found and can be initialized successfully.


Default: true

Control the use of interrupt remapping (DMA remapping will always be enabled if IOMMU functionality is enabled).

qinval (VT-d)

Default: true

Control the use of Queued Invalidation.

snoop (Intel)

Default: true

Control the use of Snoop Control.


Default: true

Control whether CPU and IOMMU page tables should be shared.


Default: false

Control whether to disable DMA remapping for Dom0.


Default: false

Control whether to set up DMA remapping only for the memory Dom0 actually got assigned. Implies no-dom0-passthrough.


Default: true

Control whether to set up interrupt remapping data structures per device rather that once for the entire system. Turning this off is making PCI device pass-through insecure and hence unsupported.

workaround_bios_bug (VT-d)

Default: false

Causes DRHD entries without any PCI discoverable devices under them to be ignored (normally IOMMU setup fails if any of the devices listed by a DRHD entry aren't PCI discoverable).


Default: false

Increase IOMMU code's verbosity.


Default: false

Enable IOMMU debugging code (implies verbose).

iommu_inclusive_mapping (VT-d)

= <boolean>

Default: false

Use this to work around firmware issues providing correct RMRR entries. Rather than only mapping RAM pages for IOMMU accesses for Dom0, with this option all pages not marked as unusable in the E820 table will get a mapping established.


= <integer>




Force the use of [<seg>:]<bus>:<device>.<func> as device ID of HPET <hpet> instead of the one specified by the IVHD sub-tables of the IVRS ACPI table.



Force the use of [<seg>:]<bus>:<device>.<func> as device ID of IO-APIC <ioapic> instead of the one specified by the IVHD sub-tables of the IVRS ACPI table.


= <boolean>

Force the use of use of the local APIC on a uniprocessor system, even if left disabled by the BIOS.


= <boolean>


= <boolean>


= <level>[/<rate-limited level>] where level is none | error | warning | info | debug | all

Default: loglvl=warning

Set the logging level for Xen. Any log message with equal more more importance will be printed.

The optional <rate-limited level> option instructs which severities should be rate limited.


= none | min | all

Default: none if not specified at all, or to min if low_crashinfo is present without qualification.

This option is only useful for hosts with a 32bit dom0 kernel, wishing to use kexec functionality in the case of a crash. It represents which data structures should be deliberately allocated in low memory, so the crash kernel may find find them. Should be used in combination with crashinfo_maxaddr.


= <integer>


= <integer>

Specifies the number of interrupts to be use for pin (IO-APIC or legacy PIC) based interrupts. Any higher IRQs will be available for use via PCI MSI.


= <integer>


= <integer>


= <integer>


= verbose

Specify verbose machine check output.


= <size>

Specify the maximum address of physical RAM. Any RAM beyond this limit is ignored by Xen.


= <boolean>[,amd-fam10]

Default: 1

Specify if the MMConfig space should be enabled.


= <boolean>

Default: true

Force Xen to (not) use PCI-MSI, even if ACPI FADT says otherwise.


= <boolean>

Default: false

Print boot time MTRR state (x86 only).


= <boolean>

Default: true

Use the MWAIT idle driver (with model specific C-state knowledge) instead of the ACPI based one.


= ignore | dom0 | fatal

Default: nmi=fatal

Specify what Xen should do in the event of an NMI parity or I/O error. ignore discards the error; dom0 causes Xen to report the error to dom0, while 'fatal' causes Xen to print diagnostics and then hang.


Instruct Xen to ignore any IOAPICs that are present in the system, and instead continue to use the legacy PIC. This is not recommended with pvops type kernels.

Because responsibility for APIC setup is shared between Xen and the domain 0 kernel this option is automatically propagated to the domain 0 command line.


= <boolean>


= <boolean>

Disable software IRQ balancing and affinity. This can be used on systems such as Dell 1850/2850 that have workarounds in hardware for IRQ routing issues.


= <boolean>

Default: false

Ignore the local APIC on a uniprocessor system, even if enabled by the BIOS.

no-real-mode (x86)

= <boolean>

Do not execute real-mode bootstrap code when booting Xen. This option should not be used except for debugging. It will effectively disable the vga option, which relies on real mode to set the video mode.


= <boolean>

Do not automatically reboot after an error. This is useful for catching debug output. Defaults to automatically reboot after 5 seconds.


= <boolean>

Disable CPU serial number reporting.


= <boolean>

Disable SMP support. No secondary processors will be booted. Defaults to booting secondary processors.


= <integer>


= on | off | fake=<integer> | noacpi

Default: on


= {no-}serr | {no-}perr

Disable signaling of SERR (system errors) and/or PERR (parity errors) on all PCI devices.

Default: Signaling left as set by firmware.



Mark a group of PCI devices as using phantom functions without actually advertising so, so the IOMMU can create translation contexts for them.

All numbers specified must be hexadecimal ones.

This option can be specified more than once (up to 8 times at present).


= <integer>


= <integer>


= t[riple] | k[bd] | a[cpi] | p[ci] | n[o] [, [w]arm | [c]old]

Default: 0

Specify the host reboot method.

warm instructs Xen to not set the cold reboot flag.

cold instructs Xen to set the cold reboot flag.

no instructs Xen to not automatically reboot after panics or crashes.

triple instructs Xen to reboot the host by causing a triple fault.

kbd instructs Xen to reboot the host via the keyboard controller.

acpi instructs Xen to reboot the host using RESET_REG in the ACPI FADT.

pci instructs Xen to reboot the host using PCI reset register (port CF9).


= credit | credit2 | sedf | arinc653

Default: sched=credit

Choose the default scheduler.


= <integer>


= <integer>

Set the timeslice of the credit1 scheduler, in milliseconds. The default is 30ms. Reasonable values may include 10, 5, or even 1 for very latency-sensitive workloads.


= <integer>

In order to limit the rate of context switching, set the minimum amount of time that a vcpu can be scheduled for before preempting it, in microseconds. The default is 1000us (1ms). Setting this to 0 disables it altogether.


= <boolean>

Normally Xen will try to maximize performance and cache utilization by spreading out vcpus across as many different divisions as possible (i.e, numa nodes, sockets, cores threads, &c). This often maximizes throughput, but also maximizes energy usage, since it reduces the depth to which a processor can sleep.

This option inverts the logic, so that the scheduler in effect tries to keep the vcpus on the smallest amount of silicon possible; i.e., first fill up sibling threads, then sibling cores, then sibling sockets, &c. This will reduce performance somewhat, particularly on systems with hyperthreading enabled, but should reduce power by enabling more sockets and cores to go into deeper sleep states.


= <size>

Default: 16kB

Set the serial transmit buffer size.


= <boolean>

Default: true

Flag to enable Supervisor Mode Execution Protection


= <boolean>

Default: true

Flag to enable Supervisor Mode Access Prevention


= <boolean>


= <boolean>

Default: false

Flag to force synchronous console output. Useful for debugging, but not suitable for production environments due to incurred overhead.


= 0x<phys_addr>

Specify the physical address of the trusted boot shared page.


= <integer>

Specify the per-cpu trace buffer size in pages.


= <boolean>

Default: true

Flag to enable TSC deadline as the APIC timer mode.


= <integer>

Specify a mask for Xen event tracing. This allows Xen tracing to be enabled at boot. Refer to the xentrace(8) documentation for a list of valid event mask values. In order to enable tracing, a buffer size (in pages) must also be specified via the tbuf_size parameter.


= <boolean>


= <integer>


= <boolean>


= <boolean>


= <boolean>


= <integer>


= <boolean>


= <integer>


= unstable | skewed


= [<integer> | scan]

Specify how and where to find CPU microcode update blob.

'integer' specifies the CPU microcode update blob module index. When positive, this specifies the n-th module (in the GrUB entry, zero based) to be used for updating CPU micrcode. When negative, counting starts at the end of the modules in the GrUB entry (so with the blob commonly being last, one could specify ucode=-1). Note that the value of zero is not valid here (entry zero, i.e. the first module, is always the Dom0 kernel image). Note further that use of this option has an unspecified effect when used with xen.efi (there the concept of modules doesn't exist, and the blob gets specified via the ucode=<filename> config file/section entry; see EFI configuration file description).

'scan' instructs the hypervisor to scan the multiboot images for an cpio image that contains microcode. Depending on the platform the blob with the microcode in the cpio name space must be: - on Intel: kernel/x86/microcode/GenuineIntel.bin - on AMD : kernel/x86/microcode/AuthenticAMD.bin


= <boolean>


= <integer>

Default: 0

Specify a delay, in microseconds, between migrations of a VCPU between PCPUs when using the credit1 scheduler. This prevents rapid fluttering of a VCPU between CPUs, and reduces the implicit overheads such as cache-warming. 1ms (1000) has been measured as a good value.


= <integer>


= <integer>


= <integer>


= ( ask | current | text-80x<rows> | gfx-<width>x<height>x<depth> | mode-<mode> )[,keep]

ask causes Xen to display a menu of available modes and request the user to choose one of them.

current causes Xen to use the graphics adapter in its current state, without further setup.

text-80x<rows> instructs Xen to set up text mode. Valid values for <rows> are 25, 28, 30, 34, 43, 50, 80

gfx-<width>x<height>x<depth> instructs Xen to set up graphics mode with the specified width, height and depth.

mode-<mode> instructs Xen to use a specific mode, as shown with the ask option. (N.B menu modes are displayed in hex, so <mode> should be a hexadecimal number)

The optional keep parameter causes Xen to continue using the vga console even after dom0 has been started. The default behaviour is to relinquish control to dom0.

vpid (Intel)

= <boolean>

Default: true

Use Virtual Processor ID support if available. This prevents the need for TLB flushes on VM entry and exit, increasing performance.


= ( bts )

Default: off

Switch on the virtualized performance monitoring unit for HVM guests.

If the current cpu isn't supported a message like
'VPMU: Initialization failed. ...'
is printed on the hypervisor serial log.

For some Intel Nehalem processors a quirk handling exist for an unknown wrong behaviour (see handle_pmc_quirk()).

If 'vpmu=bts' is specified the virtualisation of the Branch Trace Store (BTS) feature is switched on on Intel processors supporting this feature.

Warning: As the BTS virtualisation is not 100% safe and because of the nehalem quirk don't use the vpmu flag on production systems with Intel cpus!


= <boolean>

Default: false

Run an NMI watchdog on each processor. If a processor is stuck for longer than the watchdog_timeout, a panic occurs.


= <integer>

Default: 5

Set the NMI watchdog timeout in seconds. Specifying 0 will turn off the watchdog.


= <boolean>

Default: true

Permit use of x2apic setup for SMP environments.


= <boolean>

Default: true

Use the x2apic physical apic driver. The alternative is the x2apic cluster driver.


= <boolean>

Default: true

Permit use of the xsave/xrstor instructions.