Searched refs:standby (Results 1 – 9 of 9) sorted by relevance
/qemu/docs/system/ |
H A D | virtio-net-failover.rst | 2 QEMU virtio-net standby (net_failover) 5 This document explains the setup and usage of virtio-net standby feature which 14 The two devices are called primary and standby device. The fast hardware based 16 standby device. 24 and standby devices are not plugged into the same PCIe slot. 29 Virtio-net standby allows easy migration while using a passed-through fast 50 failover_pair_id references the id of the virtio-net standby device. This 57 Both primary and standby device can be hotplugged via the QEMU monitor. Note 68 when the feature bit was negotiated for the virtio-net standby device.
|
/qemu/tests/qemu-iotests/ |
H A D | 109.out | 43 …croseconds": TIMESTAMP}, "event": "JOB_STATUS_CHANGE", "data": {"status": "standby", "id": "src"}} 45 …croseconds": TIMESTAMP}, "event": "JOB_STATUS_CHANGE", "data": {"status": "standby", "id": "src"}} 94 …croseconds": TIMESTAMP}, "event": "JOB_STATUS_CHANGE", "data": {"status": "standby", "id": "src"}} 96 …croseconds": TIMESTAMP}, "event": "JOB_STATUS_CHANGE", "data": {"status": "standby", "id": "src"}} 145 …croseconds": TIMESTAMP}, "event": "JOB_STATUS_CHANGE", "data": {"status": "standby", "id": "src"}} 147 …croseconds": TIMESTAMP}, "event": "JOB_STATUS_CHANGE", "data": {"status": "standby", "id": "src"}} 196 …croseconds": TIMESTAMP}, "event": "JOB_STATUS_CHANGE", "data": {"status": "standby", "id": "src"}} 198 …croseconds": TIMESTAMP}, "event": "JOB_STATUS_CHANGE", "data": {"status": "standby", "id": "src"}} 247 …croseconds": TIMESTAMP}, "event": "JOB_STATUS_CHANGE", "data": {"status": "standby", "id": "src"}} 249 …croseconds": TIMESTAMP}, "event": "JOB_STATUS_CHANGE", "data": {"status": "standby", "id": "src"}} [all …]
|
H A D | 219.out | 54 {"data": {"id": "job0", "status": "standby"}, "event": "JOB_STATUS_CHANGE", "timestamp": {"microsec… 55 {"return": [{"current-progress": 4194304, "id": "job0", "status": "standby", "total-progress": 4194… 61 {"data": {"id": "job0", "status": "standby"}, "event": "JOB_STATUS_CHANGE", "timestamp": {"microsec… 62 {"return": [{"current-progress": 4194304, "id": "job0", "status": "standby", "total-progress": 4194… 68 {"data": {"id": "job0", "status": "standby"}, "event": "JOB_STATUS_CHANGE", "timestamp": {"microsec… 69 {"return": [{"current-progress": 4194304, "id": "job0", "status": "standby", "total-progress": 4194… 75 {"data": {"id": "job0", "status": "standby"}, "event": "JOB_STATUS_CHANGE", "timestamp": {"microsec… 76 {"return": [{"current-progress": 4194304, "id": "job0", "status": "standby", "total-progress": 4194…
|
H A D | 185.out | 173 …seconds": TIMESTAMP}, "event": "JOB_STATUS_CHANGE", "data": {"status": "standby", "id": "mirror"}} 175 …seconds": TIMESTAMP}, "event": "JOB_STATUS_CHANGE", "data": {"status": "standby", "id": "mirror"}} 198 …seconds": TIMESTAMP}, "event": "JOB_STATUS_CHANGE", "data": {"status": "standby", "id": "commit"}} 200 …seconds": TIMESTAMP}, "event": "JOB_STATUS_CHANGE", "data": {"status": "standby", "id": "commit"}}
|
/qemu/include/hw/s390x/ |
H A D | sclp.h | 162 uint16_t standby; member
|
/qemu/qapi/ |
H A D | job.json | 59 # @standby: The job is ready, but paused. This is nearly identical to 86 'data': ['undefined', 'created', 'running', 'paused', 'ready', 'standby',
|
H A D | run-state.json | 232 # S3 state, which is sometimes called standby state
|
H A D | net.json | 952 # virtio-net standby device.
|
/qemu/pc-bios/ |
H A D | canyonlands.dts | 114 standby = <0xfeff791d>;
|