migration: emit migration lifecycle events#107
Merged
Coffeeri merged 2 commits intocyberus-technology:gardenlinuxfrom Mar 27, 2026
Merged
migration: emit migration lifecycle events#107Coffeeri merged 2 commits intocyberus-technology:gardenlinuxfrom
Coffeeri merged 2 commits intocyberus-technology:gardenlinuxfrom
Conversation
7397dca to
e446a43
Compare
7c40532 to
c954939
Compare
ca32aa5 to
9df7dbc
Compare
phip1611
reviewed
Mar 16, 2026
7d8dfe6 to
543df1d
Compare
Member
|
I think we can merge this savely. It streamlines the state with upstream but can't break anything as libvirt/ch doesn't know these events so far |
Emit migration lifecycle events via the event monitor.
This aligns migration with other VM lifecycle operations such as boot,
pause, and resume, allowing external management software to observe
migration progress consistently.
Events emitted:
src:
vm.migration-started
vm.migration-finished
vm.migration-failed
vm.migration-cancelled
dst:
vm.migration-receive-started
vm.migration-receive-finished
vm.migration-receive-failed
Co-authored-by: Philipp Schuster <philipp.schuster@cyberus-technology.de>
On-behalf-of: SAP philipp.schuster@sap.com
On-behalf-of: SAP leander.kohler@sap.com
Signed-off-by: Leander Kohler <leander.kohler@cyberus-technology.de>
Emit a "vm.migration-memory-iteration" event after every precopy memory iteration to allow management software to observe forward progress during migration. This event is primarily intended for integration with management software such as libvirt, where it maps to VIR_DOMAIN_EVENT_ID_MIGRATION_ITERATION. The event is intentionally independent of any upcoming migration metrics endpoint. Detailed migration statistics will be exposed via that endpoint, while this event provides a lightweight progress signal expected by external management layers. With this event, management software can detect forward progress during migration without being blocked on any upcoming migration metrics endpoint. Co-authored-by: Philipp Schuster <philipp.schuster@cyberus-technology.de> On-behalf-of: SAP philipp.schuster@sap.com On-behalf-of: SAP leander.kohler@sap.com Signed-off-by: Leander Kohler <leander.kohler@cyberus-technology.de>
543df1d to
eda2eff
Compare
Member
|
For the record: This just streamlines with upstream. It does not change anything in libvirt/ch at the moment. |
hertrste
approved these changes
Mar 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR ports and adapts the changes from @phip1611 in cloud-hypervisor#7799.
The goal is to simplify the propagation of migration-related events within libvirt, easing integration with libvirt's implementation and laying the groundwork for https://github.com/cobaltcore-dev/cobaltcore/issues/331.
Emitted events
Source:
Destination: