Home
last modified time | relevance | path

Searched refs:postcopy (Results 1 – 23 of 23) sorted by relevance

/openbmc/qemu/docs/devel/migration/
H A Dpostcopy.rst10 the postcopy phase, a failure of *either* side causes the guest to be lost.
12 In postcopy the destination CPUs are started before all the memory has been
17 doesn't finish in a given time the switch is made to postcopy.
19 Enabling postcopy
22 To enable postcopy, issue this command on the monitor (both source and
25 ``migrate_set_capability postcopy-ram on``
32 will now cause the transition from precopy to postcopy.
36 Blocktime is a postcopy live migration metric, intended to show how
40 side. To enable postcopy blocktime calculation, enter following
43 ``migrate_set_capability postcopy-blocktime on``
[all …]
H A Dfeatures.rst9 postcopy
H A DCPR.rst146 cpr-reboot mode may not be used with postcopy, background-snapshot,
H A Dmain.rst586 This is primarily used by postcopy, but is also used to return a success
600 Return path - opened by main thread, written by main thread AND postcopy
/openbmc/qemu/qapi/
H A Dmigration.json38 # @postcopy-requests: The number of page requests received from the
55 # @postcopy-bytes: The number of bytes sent during the post-copy phase
71 'postcopy-requests': 'int', 'page-size': 'int',
74 'postcopy-bytes': 'uint64',
140 # @postcopy-active: like active, but now in postcopy mode. (since
143 # @postcopy-paused: during postcopy but paused. (since 3.0)
145 # @postcopy-recover-setup: setup phase for a postcopy recovery
148 # @postcopy-recover: trying to recover from a paused postcopy. (since
171 'active', 'postcopy-active', 'postcopy-paused',
172 'postcopy-recover-setup',
[all …]
/openbmc/qemu/tests/qemu-iotests/
H A D20185 _send_qemu_cmd $dest 'migrate_set_capability postcopy-ram on' "(qemu)"
99 _send_qemu_cmd $src 'migrate_set_capability postcopy-ram on' "(qemu)"
H A D201.out7 === Set 'migrate_set_capability postcopy-ram on' and migrate ===
H A D181.out18 === Do postcopy migration to destination ===
H A D194.out13 {"execute": "migrate-start-postcopy", "arguments": {}}
H A D18191 echo === Do postcopy migration to destination ===
/openbmc/qemu/migration/
H A Dsavevm.h39 int qemu_savevm_state_iterate(QEMUFile *f, bool postcopy);
H A Dmeson.build29 'postcopy-ram.c',
H A Dtrace-events193 process_incoming_migration_co_end(int ret, int ps) "ret=%d postcopy-state=%d"
275 # postcopy-ram.c
348 dirty_bitmap_save_iterate(int in_postcopy) "in postcopy: %d"
H A Dsavevm.c1374 int qemu_savevm_state_iterate(QEMUFile *f, bool postcopy) in qemu_savevm_state_iterate() argument
1399 if (postcopy && in qemu_savevm_state_iterate()
/openbmc/linux/Documentation/admin-guide/mm/
H A Duserfaultfd.rst265 QEMU/KVM is using the ``userfaultfd`` syscall to implement postcopy live
270 KVM kernel code had to be modified in order to add postcopy live
280 just before starting postcopy live migration, in order to avoid
283 The implementation of postcopy live migration currently uses one
294 A different postcopy thread in the destination node listens with
296 generated after a userfault triggers, the postcopy thread read() from
301 After the QEMU postcopy thread (running in the destination node) gets
322 postcopy thread just before ``UFFDIO_COPY|ZEROPAGE`` runs in the migration
/openbmc/qemu/docs/system/
H A Dvm-templating.rst123 destination early and refuses to activate postcopy live migration. Note
124 that postcopy live migration usually only works on selected filesystems
/openbmc/qemu/hw/vfio/
H A Dtrace-events168 …int64_t precopy, uint64_t postcopy, uint64_t precopy_init_size, uint64_t precopy_dirty_size) " (%s…
169 …opy, uint64_t postcopy, uint64_t stopcopy_size, uint64_t precopy_init_size, uint64_t precopy_dirty…
/openbmc/qemu/
H A Dhmp-commands.hx915 "\n\t\t\t -r to resume a paused postcopy migration",
928 Resume a paused postcopy migration.
974 .help = "Continue a paused incoming postcopy migration",
980 Continue a paused incoming postcopy migration using the *uri*.
987 .help = "Pause an ongoing migration (postcopy-only)",
993 Pause an ongoing migration. Currently it only supports postcopy.
1029 " to postcopy mode. The postcopy-ram capability must "
1037 Switch in-progress migration to postcopy mode. Ignored after the end of
1038 migration (or once already in postcopy).
/openbmc/qemu/docs/interop/
H A Dvhost-user.rst577 In postcopy migration the back-end is started before all the memory has
1142 :reply payload: (postcopy only) multiple memory regions description
1471 advises back-end that a migration with postcopy enabled is underway,
1480 The front-end advises back-end that a transition to postcopy mode has
1492 The front-end advises that postcopy migration has now completed. The back-end
1596 In postcopy mode (see ``VHOST_USER_POSTCOPY_LISTEN``), the back-end
1598 For further details on postcopy, see ``VHOST_USER_SET_MEM_TABLE``.
H A Dqmp-spec.rst330 "desc": "migrate-pause is currently only supported during postcopy-active state" } }
/openbmc/qemu/docs/devel/
H A Dqapi-code-gen.rst570 enabled for postcopy live migration.
/openbmc/linux/
H A Dopengrok0.0.log2640 2024-12-28 20:09:06.452-0600 FINEST t1118 PendingFileCompleter.doRename: Moved pending as file: '/opengrok/data/xref/openbmc/qemu/migration/postcopy-ram.c.gz'
[all...]
H A Dopengrok1.0.log[all...]