Lines Matching refs:dom0
466 Xen and dom0. The required sequence is CTRL-<switch char> three
470 switch the console input to dom0 during boot. Any other value,
471 including omission, causes Xen to automatically switch to the dom0
472 console during dom0 boot. Use `conswitch=ax` to keep the default switch
487 …[:[powersave|performance|ondemand|userspace][,<maxfreq>][,[<minfreq>][,[verbose]]]]} | dom0-kernel`
492 choice of `dom0-kernel` is deprecated and not supported by all Dom0 kernels.
700 ### dom0
706 Controls for how dom0 is constructed on x86 systems.
708 * The `pv` and `pvh` options select the virtualisation mode of dom0.
716 * The dom0 kernel selected by the boot loader must be capable of the
718 * For a PVH dom0, the hardware must have VT-x/SVM extensions available.
720 * The `shadow` boolean allows dom0 to be explicitly constructed using shadow
724 For PVH, dom0 defaults to using HAP on capable hardware, and falls back to
725 shadow paging otherwise. A PVH dom0 cannot be used if Xen is compiled
728 For PV, the use of dom0 shadow mode is only for development purposes. PV
732 information during the dom0 build. It defaults to the compile time choice
736 PV dom0, and defaults to true.
740 Faulting was never activated for PV dom0's, even on capable hardware.
744 even for PV dom0's.
746 However, as PV dom0's have always seen host CPUID data in the past, there
749 an issue in dom0, please report a bug.
751 ### dom0-iommu
755 Controls for the dom0 IOMMU setup.
758 is disabled for devices in dom0 (`passthrough=1`) or whether the IOMMU is
759 used to ensure that dom0 can only DMA to its permitted areas of RAM
762 This option is only applicable to x86 PV dom0's, and defaults to false.
769 This option is hardwired to false for x86 PVH dom0's (where a non-identity
770 transform is required for dom0 to function), and is ignored for ARM.
772 * The `strict` boolean is applicable to x86 PV dom0's only and defaults to
773 false. It controls whether dom0 can have IOMMU mappings for all domain
776 This option is hardwired to true for x86 PVH dom0's (as RAM belonging to
780 * The `map-inclusive` boolean is applicable to x86 PV dom0's, and sets up
800 to both x86 PV and PVH dom0's, is enabled by default, and represents a
806 dom0 to boot.
813 Specify a list of IO ports to be excluded from dom0 access.
821 The number of VCPUs to give to dom0. This number of VCPUs can be more
829 Gives dom0 a number of VCPUs equal to the number of PCPUs, but always
847 Set the amount of memory for the initial domain (dom0). It must be
853 Set the amount of memory for the initial domain (dom0). If a size is
870 memory dom0 can balloon up to). If this is omitted then the maximum
873 For example, to set dom0's initial memory allocation to 512MB but
884 any dom0 autoballooning feature present in your toolstack. See the
907 Pin dom0 vcpus to their respective pcpus
953 dom0. Selecting `rs=0` prohibits all use of Runtime Services.
1018 > `= [<domU number>][,<dom0 number>]`
1024 is for dom0. Changing the setting for domU has no impact on dom0 and vice
1025 versa. For example to change dom0 without changing domU, use
1028 Note that specifying zero as domU value means zero, while for dom0 it means
1284 dom0-{passthrough,strict} ]
1394 **WARNING: The `dom0-passthrough` and `dom0-strict` booleans are both
1467 This option is only useful for hosts with a 32bit dom0 kernel, wishing
1478 Specify the threshold below which Xen will inform dom0 that the quantity of
1577 > `= ignore | dom0 | fatal`
1579 > Default: `fatal` for a debug build, or `dom0` for a non-debug build
1582 `ignore` discards the error; `dom0` causes Xen to report the error to
1583 dom0, while 'fatal' causes Xen to print diagnostics and then hang.
1772 > `= List of [ <bool>, dom0=<bool>, domu=<bool> ]`
2293 console even after dom0 has been started. The default behaviour is to
2294 relinquish control to dom0.
2435 > `= List of [ default | <boolean> | dom0=<bool> | domu=<bool> ]`
2450 With `dom0` and `domu` it is possible to control page table isolation
2451 for dom0 or guest domains only.