do not reset migration state on device reset (#844)#854
Merged
Conversation
Collaborator
|
Apologies for the delay, I somehow missed the original email notification, will review this shortly. |
tmakatos
approved these changes
May 7, 2026
Collaborator
|
@Hooollin can you rebase? |
Unconditionally resetting migration state to RUNNING on device reset caused desynchronization with migration initiators(e.g. QEMU) when a reset occurred during the pre-copy phase, leading to invalid state transitions and aborted migrations. The reset operation should only discard captured device state, not modify the active migration state machine. Signed-off-by: liuhaolin <hollinisme@gmail.com>
Hooollin
force-pushed
the
fix-migration-reset-state
branch
from
acc4616 to
0acd12d
Compare
Contributor
Author
Done. |
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
3 participants
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.
Unconditionally resetting migration state to RUNNING on device reset caused desynchronization with migration initiators(e.g. QEMU) when a reset occurred during the pre-copy phase, leading to invalid state transitions and aborted migrations.
The reset operation should only discard captured device state, not modify the active migration state machine.