Home
last modified time | relevance | path

Searched refs:running (Results 1 – 25 of 97) sorted by relevance

1234

/xen/docs/misc/
A Dqemu-backends.txt6 from the domain id where the qemu instance is running $BACKEND_DOM,
11 Before signalling qemu is running by writing "running" to $QEMU/state
14 for the qdisk backend). In case qemu is running de-privileged (not as
A Dstubdom.txt30 qemu-traditional running in MiniOS stubdomain. The protocol include
55 3. stubdomain signal readiness by writing "running" to /local/domain/<stubdom-id>/device-model/<tar…
56 4. now stubdomain is considered running
63 4. Write "running" back to /local/domain/<stubdom-id>/device-model/<target-id>/state.
75 - "running" - success
82 qemu-upstream running in Linux stubdomain. The protocol include
119 5. qemu signal readiness by writing "running" to /local/domain/<stubdom-id>/device-model/<target-id…
120 6. now device model is considered running
186 By running
A Dxenpaging.txt12 memory. This allows the sum of all running guests to use more memory
28 Once the guest is running, run xenpaging with the guest_id and the path
A Dvtd-pi.txt36 assignment requirements. However, today when a VM is running with
47 - Direct delivery of external interrupts to running vCPUs without VMM
62 When a VM is running and an external interrupt from an assigned device occurs
80 However, after VT-d PI is supported, when a guest is running in non-root and an
252 1. When vCPU is running
255 - Set 'NDST' to the pCPU on which the vCPU will be running.
275 1. vCPU0 is running on pCPU0
276 2. vCPU0 is blocked and vCPU1 is currently running on pCPU0
295 to the per-cpu list belonging to the pCPU it was running.
326 interrupts from the same device (like NIC) will start running on all the CPUs
A Dkexec_and_kdump.txt8 And will thus affect all guests running on a machine.
53 need to be loaded into the running hypervisor or kernel using
161 Once you are running in a kexec-enabled hypervisor and dom0,
163 running kernel.
/xen/tools/ocaml/test/
A Dlist_domains.ml7 and running = bool_as_char dominfo.Xenlight.Dominfo.running 'r'
14 printf "Dom %d: %c%c%c%c%c %LdKB\n" id running blocked paused shutdown dying memory
/xen/docs/
A Dglossary.rst27 The numeric identifier of a running :term:`domain`. It is unique to a
36 machine which is the "useful output" of running the system in the first
43 In this case, it refers to all code running lower privilege privilege
A Dindex.rst47 who is building Xen from source, and is running the new hypervisor in some
/xen/tools/libxl/
A Dlibxl_stream_read.c212 stream->running = false; in libxl__stream_read_init()
234 stream->running = true; in libxl__stream_read_start()
299 assert(stream->running); in libxl__stream_read_start_checkpoint()
317 if (stream->running) in libxl__stream_read_abort()
742 assert(stream->running); in stream_complete()
799 assert(stream->running); in stream_done()
802 stream->running = false; in stream_done()
955 assert(stream->running); in libxl__stream_read_checkpoint_state()
A Dlibxl_stream_write.c214 stream->running = false; in libxl__stream_write_init()
238 stream->running = true; in libxl__stream_write_start()
291 assert(stream->running); in libxl__stream_write_start_checkpoint()
304 if (stream->running) in libxl__stream_write_abort()
576 assert(stream->running); in stream_complete()
611 assert(stream->running); in stream_done()
613 stream->running = false; in stream_done()
694 assert(stream->running); in libxl__stream_write_checkpoint_state()
/xen/automation/build/
A DREADME.md6 running Docker. They are organized by distro and tagged with
37 - DOCKED_CMD: Whether to use docker or podman for running the containers.
41 docker is the default, for running with podman, do:
87 for you. If you define the `PUSH` environment variable when running the
/xen/tools/hotplug/Linux/init.d/
A Dsysconfig.xendomains.in50 # Directory to save running domains to when the system (dom0) is
74 # might want to shutdown the virtual machines that are still running
100 # in AUTO which are not running yet.
111 # all running domains will be.
126 # zombies are still running, so you don't need to enable this timeout just
/xen/xen/arch/arm/tee/
A DKconfig7 OP-TEE running on your platform. This requires
/xen/xen/common/
A Dgdbstub.c544 .running = ATOMIC_INIT(1),
591 if ( !atomic_dec_and_test(&gdb_ctx->running) ) in __trap_to_gdb()
594 atomic_inc(&gdb_ctx->running); in __trap_to_gdb()
636 atomic_inc(&gdb_ctx->running); in __trap_to_gdb()
A Dtimer.c36 struct timer *running; member
416 BUG_ON(this_cpu(timers).running == timer); in kill_timer()
432 while ( per_cpu(timers, cpu).running == timer ) in kill_timer()
445 ts->running = t; in execute_timer()
449 ts->running = NULL; in execute_timer()
/xen/docs/man/
A Dxen-tscmode.7.pod16 equally to both the OS and ALL apps that are running on this
31 or any running apps? If the sum exceeds about 10,000 rdtsc instructions
69 TSC-sensitive apps are running and it is necessary to understand
75 is certain that all apps running in this VM are TSC-resilient and
154 tasks when running on these recent machines.
165 We will refer to apps that might break if running on a TSC-unsafe
172 a guest OS and all its currently running applications may be invisibly
221 or a tsc_mode==3 domain when it is running on TSC-unsafe hardware.
252 to disable migration. If no_migrate is selected and the VM is running
/xen/xen/include/xen/
A Dgdbstub.h32 atomic_t running; member
/xen/tools/tests/mce-test/tools/
A DREADME6 software level into a running Xen/dom0/VM. This is intended for
/xen/config/
A DPaths.mk.in6 # and is generated after running ./configure. The master source is located
/xen/tools/xenmon/
A Dxenbaked.c108 int *running = NULL; variable
122 running = calloc(ncpu, sizeof(int)); in init_current()
132 if (running[cpu] == domain) in is_current()
142 return running[cpu];
148 running[cpu] = domain; in set_current()
/xen/tools/debugger/gdbsx/
A DREADME6 kernel modules. It runs on dom0 running on xen hypervisor and allows debug
56 - make sure firewall is disabled on dom0 if running gdb on a different host.
/xen/docs/features/
A Dmigration.pandoc18 running. Live migration moves a running virtual machine between two
/xen/docs/designs/
A Dnon-cooperative-migration.md7 running under Xen and is hence expected to co-operate. This model dates from
9 least the privileged software running in the guest (i.e. the guest kernel)
13 running in the guest, and is thus suitable for cloud scenarios.
180 domain running the backend, which it discovers using the `backend-id` node
196 to avoid the need for explicit action by frontend drivers running in the
203 early in migration, the toolstack running on the remote host would set up a
206 running in the source domain. For non-cooperative migration these channels
/xen/docs/specs/
A Dlibxl-migration-stream.pandoc17 The _domain image format_ is the context of a running domain used for
281 In COLO, Primary is running in below loop:
294 While Secondary is running in below loop:
/xen/
A DCHANGELOG.md20 - libxl support for running qemu-xen device model in a linux stubdomain.

Completed in 33 milliseconds

1234