4 ms·
Good point. The naming of those frameworks is sooo confusing. IMHO, nearly impossible to not mix them up.
by cpach 9mo ago
Good point. The naming of those frameworks is sooo confusing. IMHO, nearly impossible to not mix them up.
- carlm42 9mo agoMy mental model is that each of these covers a different layer of the stack, from lowest to highest: * hypervisor-framework handles the hypervisor bits, like creating virtual machines, virtualising hardware resources, basically a C API on top of Apple's hypervisor * virtualization-framework is a higher-level API, meant to make it easy to run a full-blown VM with an OS and hardware integration, without having to reinvent the integration with lower-level primitives that hypervisor-framework provides * containerization-framework uses virtualization-framework to run Linux containers on macOS in microVMs. By analogy to not mix them up, it's a bit like KVM > QEMU > containerd. Hope this helps!
- Angostura 9mo agoWell, it help me. So thanks!