Searched refs:started (Results 1 – 21 of 21) sorted by relevance
/xen-4.10.0-shim-comet/tools/hotplug/Linux/init.d/ |
A D | sysconfig.xendomains.in | 27 # 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-4.10.0-shim-comet/tools/examples/ |
A D | xlexample.pvhlinux | 16 # The default behavior is to generate a new UUID each time the guest is started.
|
A D | xlexample.pvlinux | 13 # The default behavior is to generate a new UUID each time the guest is started.
|
A D | xlexample.hvm | 16 # The default behavior is to generate a new UUID each time the guest is started.
|
/xen-4.10.0-shim-comet/docs/misc/ |
A D | xenpaging.txt | 26 started manually for each guest.
|
A D | xenmon.txt | 74 - Start xenmon by simply running xenmon.py; The xenbake demon is started and
|
A D | xenstore.txt | 229 tx_id request header field. When transaction is started whole
|
A D | xenstore-paths.markdown | 566 The time which the guest was started in SECONDS.MICROSECONDS format
|
A D | xen-command-line.markdown | 1774 console even after dom0 has been started. The default behaviour is to
|
/xen-4.10.0-shim-comet/tools/blktap2/drivers/ |
A D | tapdisk-stream.c | 74 uint64_t started; member 292 sreq->seqno = s->started++; in tapdisk_stream_enqueue()
|
A D | block-vhd.c | 168 int started; member 912 tx->started++; in add_to_transaction() 919 tx->started, tx->finished, tx->status); in add_to_transaction() 925 return (tx->started == tx->finished); in transaction_completed() 1898 if (tx->started && transaction_completed(tx)) in start_new_bitmap_transaction() 2129 blk, tx->started, tx->finished); in finish_bitmap_write() 2172 req->treq.sec / s->spb, tx->started, tx->finished); in finish_data_write() 2298 tx->started, tx->finished, tx->status, tx->requests.head, rnum); in vhd_debug()
|
A D | tapdisk-diff.c | 74 uint64_t started; member 425 sreq->seqno = s->started++; in tapdisk_stream_enqueue1()
|
/xen-4.10.0-shim-comet/docs/man/ |
A D | xen-vtpm.pod.7 | 174 The vTPM Manager domain (vtpmmgr-stubdom) must be started like any other Xen 186 The vTPM manager should be started at boot; you may wish to create an init 188 started by the domain builder to minimize the trusted computing base for the 281 often started using the pv-grub bootloader as the kernel, which then can load
|
A D | xen-pv-channel.pod.7 | 100 The VM is started
|
A D | xen-vtpmmgr.pod.7 | 232 The vTPM Manager domain (vtpmmgr-stubdom) must be started like any other Xen
|
A D | xl.pod.1.in | 114 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-4.10.0-shim-comet/ |
A D | INSTALL | 103 started with this version of the tools. Only if all domUs used the new 136 can also be started by systemd. If this option is enabled xenstored will 289 which means all dependencies will be started automatically:
|
A D | COPYING | 179 when run, you must cause it, when started running for such
|
/xen-4.10.0-shim-comet/docs/process/ |
A D | xen-release-management.pandoc | 572 I have started to include the version number of series associated to each
|
/xen-4.10.0-shim-comet/tools/xenmon/ |
A D | COPYING | 104 when run, you must cause it, when started running for such
|
/xen-4.10.0-shim-comet/xen/ |
A D | COPYING | 131 when run, you must cause it, when started running for such
|
Completed in 23 milliseconds