[Rust-VMM] Summer of Code / Outreachy projects

Josh Triplett josh at joshtriplett.org
Sat Jan 19 00:23:06 UTC 2019

On Fri, Jan 18, 2019 at 11:06:52AM +0100, Paolo Bonzini wrote:
> On 17/01/19 20:48, Cory Maccarrone wrote:
> > A port seems like a much more tractable project than a rewrite for
> > sure.  The KVM instruction emulator is more or less proven and works, so
> > reason not to port it I think.  Agreed on the intern project, it would
> > be great for that.
> A better candidate for porting is the emulator embedded in QEMU for
> Hypervisor.framework.  It's less complete (it doesn't attempt to cover
> big real mode) and less optimized, but the code is very clean.
> The question is what you'd use it for---that is, how you would embed it
> in Firecracker or crosvm.  A complete port of Firecracker/crosvm to
> Hypervisor.framework (which needs such an emulator) is a very large
> project, even though some lessons can be learnt from QEMU.  I had a
> pretty good GSoC student from 2017 and he used pretty much the whole
> summer cleaning up code taken from Android emulator code and getting it
> ready for inclusion in upstream QEMU.

I would suggest not having support in Firecracker/crosvm for hypervisors
other than Linux /dev/kvm. The instruction-set emulator can be a
separate crate, as can the virtio backends, and then someone wanting to
build a minimal hypervisor based on Hypervisor.framework can reuse those

More information about the Rust-vmm mailing list