Home
last modified time | relevance | path

Searched refs:started (Results 1 – 25 of 26) sorted by relevance

12

/xen/docs/features/
A Ddom0less.pandoc23 this way are started right away in parallel. Hence, their boot time is
95 Domains started by Xen at boot time currently have the following
103 started by Xen at boot might not work as expected.
106 information, the GIC version exposed to the domains started by Xen at
112 - Pinning vCPUs of domains started by Xen at boot can be
/xen/xen/arch/x86/hvm/viridian/
A Dtime.c122 if ( !vs->started ) in stop_stimer()
126 vs->started = false; in stop_stimer()
161 if ( !vs->started || vs->config.lazy ) in start_stimer()
207 vs->started = true; in start_stimer()
270 if ( vs->started ) in time_vcpu_freeze()
/xen/tools/hotplug/Linux/init.d/
A Dsysconfig.xendomains.in27 # to get started before creating another domain or proceeding through the
72 # started ones, see XENDOMAINS_AUTO_ONLY below) in a loop and sent SysRq,
95 # are stored that should be started on system startup automatically.
108 # If this variable is set to "true", only the domains started via config
/xen/xen/include/asm-x86/hvm/
A Dviridian.h26 bool started; member
/xen/tools/examples/
A Dxlexample.pvhlinux16 # The default behavior is to generate a new UUID each time the guest is started.
A Dxlexample.pvlinux13 # The default behavior is to generate a new UUID each time the guest is started.
A Dxlexample.hvm16 # The default behavior is to generate a new UUID each time the guest is started.
/xen/docs/guest-guide/x86/
A Dhypercall-abi.rst104 Guests which are started using the PV boot protocol may set set
113 mechanism is common for HVM guests which are typically started via legacy
/xen/docs/admin-guide/
A Dintroduction.rst13 When Xen boots, dom0 is automatically started as well. Dom0 is a virtual
/xen/docs/misc/
A Dxenpaging.txt26 started manually for each guest.
A Dxenmon.txt74 - Start xenmon by simply running xenmon.py; The xenbake demon is started and
A Dstubdom.txt53 1. PV stubdomain is started with ioemu-stubdom.gz kernel and no initrd
A Dxenstore.txt243 tx_id request header field. When transaction is started whole
A Dxenstore-paths.pandoc597 The time which the guest was started in SECONDS.MICROSECONDS format
/xen/docs/man/
A Dxen-vtpm.7.pod180 The vTPM Manager domain (vtpmmgr-stubdom) must be started like any other Xen
192 The vTPM manager should be started at boot; you may wish to create an init
194 started by the domain builder to minimize the trusted computing base for the
287 often started using the pv-grub bootloader as the kernel, which then can load
A Dxen-pv-channel.7.pod99 The VM is started
A Dxen-vtpmmgr.7.pod236 The vTPM Manager domain (vtpmmgr-stubdom) must be started like any other Xen
A Dxl.1.pod.in114 Create will return B<as soon> as the domain is started. This B<does
151 Attach console to the domain as soon as it has started. This is
/xen/docs/designs/
A Dqemu-deprivilege.md235 happen after the guest has started running, and assume QEMU has been
286 started up on the post-migration side. One issue that needs to be
288 for the domain to be started (since this is normally done via
/xen/
A DINSTALL123 started with this version of the tools. Only if all domUs used the new
156 can also be started by systemd. If this option is enabled xenstored will
308 which means all dependencies will be started automatically:
A DCOPYING181 when run, you must cause it, when started running for such
/xen/docs/hypervisor-guide/x86/
A Dhow-xen-boots.rst44 entrypoint must be started in 32bit mode.
/xen/docs/process/
A Dxen-release-management.pandoc581 I have started to include the version number of series associated to each
/xen/tools/xenmon/
A DCOPYING104 when run, you must cause it, when started running for such
/xen/xen/
A DCOPYING131 when run, you must cause it, when started running for such

Completed in 19 milliseconds

12