[WIP] migration: Persist Nested Virtualisation State #7074
Closed
Conversation
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
6 tasks
26 tasks
When the guest itself uses VMX/SVM (x86 only), this change ensures that the necessary nested state of KVM is migrated as well. Signed-off-by: Philipp Schuster <[email protected]> On-behalf-of: SAP [email protected]
Member
|
Draft PRs are meant to be temporary. The expectation is that they are either prepared for a formal review (undraft) or closed once they have served their purpose (such as gathering initial feedback). @phip1611 Please open an issue to track the work and reopen a PR when it is ready. Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
To migrate guests that use virtualisation themselves (host KVM performs nested virtualsation), we need to persist the state for live-migration and state save/resume.
This needs preliminary work in
rustvmm/kvm-rs, which you can find here:Testing
I had an intermdiate solution where I did my changes on an older version of kvm-ioctls (the one that Cloud Hypervisor refers to). There I verified that things work. Now, it will take a few steps to make everytihing compile, version bumps, ...
Steps to Undraft
kvm-ioctls to >= 0.23andkvm-bindings to >= 0.13