3 ms·
They only took, like, the network stack from Mirage. Their virtualization library is xhyve… well, turned into a library.
by floatboth 10y ago
They only took, like, the network stack from Mirage. Their virtualization library is xhyve… well, turned into a library.
- avsm 10y agoOpen sourcing our libraries is obviously just the start. We're really keen to hear about any other uses that people might have and move HyperKit in the direction of easy integration with higher-level frameworks. For instance, direct ports of unikernel projects to run against the HyperKit kexec APIs would be really fun. Any takers for MirageOS or HalVM? :-) We've started keeping a list of "help wanted" issues for anyone interested in getting started with hacking in this area: https://github.com/docker/hyperkit/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22 https://github.com/docker/hyperkit/issues?q=is%3Aissue+is%3A...
- bboreham 10y agoWhat was the motivation to create a new repo with a different name rather than maintaining a fork of xhyve?
- avsm 10y agoWe're taking it in a fairly different direction from upstream xhyve and bhyve, with the integration with other kits like VPNKit, DataKit (and soon, FSKit). We wanted to be able to diverge the build system in particular, and this makes it difficult to maintain a direct fork. However, we're committed to upstreaming patches to their relevant projects where relevant, and so the HyperKit Git repository is as close as we can make it. If it diverges a lot in the future with file renames, we'll have to figure out the Git-fu to make cherry-picks easier...