Skip to content

Conversation

CuriousGeorgiy
Copy link

Issue #, if available: #506

Description of changes:
According to the firecracker OpenAPI specification1, creating vsock devices is only a pre-boot request, so adding vsocks after loading a snapshot fails. It also seems redundant, since the VM loaded from a snapshot restores vsocks anyways.

Closes #506

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Footnotes

  1. https://github.com/firecracker-microvm/firecracker/blob/56aeeac51c00b449a45be4542b3e807d34690ba7/src/api_server/swagger/firecracker.yaml#L676-L678

According to the firecracker OpenAPI specification [1], creating vsock
devices is only a pre-boot request, so adding vsocks after loading a
snapshot fails. It also seems redundant, since the VM loaded from a
snapshot restores vsocks anyways.

Closes firecracker-microvm#506

1. https://github.com/firecracker-microvm/firecracker/blob/56aeeac51c00b449a45be4542b3e807d34690ba7/src/api_server/swagger/firecracker.yaml#L676-L678

Signed-off-by: Georgiy Lebedev <[email protected]>
@CuriousGeorgiy CuriousGeorgiy requested a review from a team as a code owner August 24, 2023 10:57
@CuriousGeorgiy
Copy link
Author

Should I add a test for this patch?

@CuriousGeorgiy
Copy link
Author

/cc @fangn2 @swagatbora90 @bduffany

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Remove addVsocksHandler from loadSnapshotHandlerList
1 participant