Lines Matching refs:dom0
428 Xen and dom0. The required sequence is CTRL-<switch char> three
432 switch the console input to dom0 during boot. Any other value,
433 including omission, causes Xen to automatically switch to the dom0
434 console during dom0 boot. Use `conswitch=ax` to keep the default switch
449 …[:[powersave|performance|ondemand|userspace][,<maxfreq>][,[<minfreq>][,[verbose]]]]} | dom0-kernel`
454 choice of `dom0-kernel` is deprecated and not supported by all Dom0 kernels.
618 ### dom0\_ioports\_disable
621 Specify a list of IO ports to be excluded from dom0 access.
623 ### dom0\_max\_vcpus
629 The number of VCPUs to give to dom0. This number of VCPUs can be more
637 Gives dom0 a number of VCPUs equal to the number of PCPUs, but always
652 ### dom0\_mem (ARM)
655 Set the amount of memory for the initial domain (dom0). It must be
658 ### dom0\_mem (x86)
661 Set the amount of memory for the initial domain (dom0). If a size is
678 memory dom0 can balloon up to). If this is omitted then the maximum
681 For example, to set dom0's initial memory allocation to 512MB but
685 any dom0 autoballooning feature present in your toolstack. See the
691 ### dom0\_nodes
703 ### dom0\_vcpus\_pin
708 Pin dom0 vcpus to their respective pcpus
710 ### dom0 subsection
719 Flag that makes a dom0 boot in PVHv2 mode.
725 Flag that makes a dom0 use shadow paging. Only works when "pvh" is
785 > `= [<domU number>][,<dom0 number>]`
791 is for dom0. Changing the setting for domU has no impact on dom0 and vice
792 versa. For example to change dom0 without changing domU, use
795 Note that specifying zero as domU value means zero, while for dom0 it means
1023 …rce | required | intremap | intpost | qinval | snoop | sharept | dom0-passthrough | dom0-strict | …
1075 > `dom0-passthrough`
1081 > `dom0-strict`
1086 >> got assigned. Implies `no-dom0-passthrough`.
1192 This option is only useful for hosts with a 32bit dom0 kernel, wishing
1203 Specify the threshold below which Xen will inform dom0 that the quantity of
1294 > `= ignore | dom0 | fatal`
1296 > Default: `fatal` for a debug build, or `dom0` for a non-debug build
1299 `ignore` discards the error; `dom0` causes Xen to report the error to
1300 dom0, while 'fatal' causes Xen to print diagnostics and then hang.
1774 console even after dom0 has been started. The default behaviour is to
1775 relinquish control to dom0.