vdpa/virtio: fix dirty logging stop #75
Merged
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.
When live migration fail on destination, source qemu will send stop logging(by
set_features
) to dpdk, virtio vdpa driver is missing sending this stop logging to controller. Start another round LM, the repeated start logging will cause controller return error and dpdk stuck in retry admin queue command.Add log_started flag to save current logging state and send log stop to controller.
RM: 3851825