Introduce a separate KVM error variant of HyperlightError. #771
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.
Fixes a common build error which occurs when the version of vmm-sys-util crate does not match between mshv/kvm.
VmmSysError variant is now solely used for our signal registration, and is not used by mshv nor kvm code.
Kvm functions like
Kvm::new()?
will ue the new variant automatically.Certain Mshv functions from mshv_bindings used to use our vmm-sys-util error, which are changed in this commit.
This error only manifests when a separate crate depends on hyperlight-host, but not when we build hyperlight-host ourselves, since we check in our cargo.lock, and dependency resolution could make crates have different versions.
The error either happened in kvm code (as seen below), or in mshv code, depending on which version of vmm-sys-util hyperlight uses