Searched refs:fail (Results 1 – 20 of 20) sorted by relevance
| /docs/ |
| A D | support-matrix-generate | 45 fail () { echo >&2 "$0: $1"; exit 12; } function
51 -*) fail 'bad usage' ;;
57 *) fail 'bad usage' ;;
91 *) fail "?? $current_url $exists ?";;
111 fail "Unable to identify Xen version for $commitish";
|
| /docs/misc/xen-makefiles/ |
| A D | makefiles.rst | 112 otherwise the command line check will fail, and the target will
119 significant; for instance, the below will fail (note the extra space
|
| /docs/man/ |
| A D | xl.conf.5.pod.in | 189 attempted as normal and may fail due to memory exhaustion.
213 masks. If the resulting affinity mask is empty, operation will fail.
|
| A D | xlcpupool.cfg.5.pod | 95 cpus must be free, or creation will fail. C<CPU-LIST> may be specified
|
| A D | xen-tscmode.7.pod | 255 saved, restore this domain will fail.
|
| A D | xl-numa-placement.7.pod | 248 bits set, as it is by default), or domain creation will fail with
|
| A D | xl.1.pod.in | 410 driver to reach the target amount of memory. The guest may fail to
1414 or is still using the device), the detach will fail.
|
| A D | xl.cfg.5.pod.in | 1299 A "strict" policy leads to a fail in libxl.
|
| /docs/designs/ |
| A D | qemu-deprivilege.md | 55 properties, and that hypercalls which are meant to fail do fail. (In
86 restrictions fail, the process won't be able to even name system mount
|
| /docs/misc/ |
| A D | crashdb.txt | 54 Reasons why we might fail to reach the debugger:
|
| A D | xen-error-handling.txt | 54 *particularly* unlikely ever to fail).
|
| A D | xenstore-paths.pandoc | 467 "0" -> the frontend should not be expected to respond, so fail the
470 do so and maybe fail the control operation after some reasonable
|
| A D | xl-psr.pandoc | 39 An attach may fail because of no free RMID available. In such case unused
|
| A D | vtd.txt | 120 regions will fail. Hence BIOS uses RMRR to specify these regions along with
|
| A D | livepatch.pandoc | 468 in the hook fail or cannot be executed.
500 in the hook fail or cannot be executed.
751 fail), `name_total_size` and `metadata_total_size` containing total sizes of
|
| A D | netif-staging-grants.pandoc | 192 21) Check if the grant operations were successful and fail transmission if
|
| A D | xen-command-line.pandoc | 651 It should be noted that dumping diagnosis data to the console can fail in
912 creation will fail and the system will stop, the same will occur if the
2675 probe only the TEE mediator passed as argument and boot will fail if this
|
| /docs/misra/ |
| A D | xen-static-analysis.rst | 50 This step is performed even in case any of the previous step fail, to skip
|
| /docs/specs/ |
| A D | libxc-migration-stream.pandoc | 252 unsupported mandatory record must fail. The contents of optional
355 Restoring an image with unrecognised page types shall fail.
|
| /docs/misc/arm/device-tree/ |
| A D | booting.txt | 224 creation will fail and the system will stop, the same will occur if the
|
Completed in 115 milliseconds