emesare / emesare/windows-hypervisor
Usage of rust-vmm crates
- Dominant language
- Rust
- Stars
- 9
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Where applicable we should use [rust-vmm] crates to increase composability and gain features (see #2) for free.
Should we introduce these to our public API? A quick look at the [kvm-ioctls] crate shows that they do not actually use any of the surrounding [rust-vmm] ecosystem, like [vm-memory]. Given that [windows-hypervisor] operates much in the same way as [kvm-ioctls] should we instead focus on a public API which provides maximum flexibility and have the consumer rely on [rust-vmm]?
[vm-memory]: https://github.com/rust-vmm/vm-memory/
[kvm-ioctls]: https://github.com/rust-vmm/kvm-ioctls/
[windows-hypervisor]: https://github.com/emesare/windows-hypervisor/
[rust-vmm]: https://github.com/rust-vmm/
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.