kata-containers VS kubevirt

QEMU is more well-known and tested than Firecracker; i.e., a hacked version is used in Xen. Cloud Hypervisor, Dragonball, and StratoVirt aren't well-known or battle-tested IMO. The problem is none of these possess true manageability and isolation features of any solid type 1 hypervisor which makes Kata a user-space application rather than a reliable platform with harder resource isolation guarantees.

https://github.com/kata-containers/kata-containers/blob/main...

Why not some of the existing microvm efforts?

Cloud Hypervisor and Firecracker both have an excellent reputation for ultra lightweight VM's. Both are usable in the very popular Kata Containers project. https://github.com/kata-containers/kata-containers

There's also smaller efforts such as Virtink, which bring Cloud Hypervisor to kubernetes. https://github.com/smartxworks/virtink

The orientation as a safe sandbox for AI / MCP tools is a very nicely packaged looking experience, and very well marketred. Congratulations! I'm still not sure why this warrants being it's own project.

You can follow this post or official document of Kata Containers here for any details.

I bet the first thing you think that it is a bug. There is an issue on GitHub where someone thought the same. The fact is that Kata containers are different and there are Limitations. The first I noticed too, that there is no way to share process or network namespaces between Docker containers. The fact that you cannot use the process namespace or network namespace of the host is easily understandable because we have a VM and not just a host kernel isolating our processes.

> I actually wonder how much "overhead" a VM actually has. i.e. a linux kernel that doesn't do anything (say perhaps just boots to an init that mounts proc and every n seconds read in/prints out /proc/meminfo) how much memory would the kernel actually be using?

There's already some memory sharing available using DAX in Kata Containers at least: https://github.com/kata-containers/kata-containers/blob/main...

Seems like Fly.io Machines are trying reimplement Kata Containers with the Firecracker backend [0].

Kata has a guest image and guest agent to run multiple isolated containers [1].

[0] https://katacontainers.io/

[1] https://github.com/kata-containers/kata-containers/blob/main...

> Last time I looked (a few months ago), the documentation was pretty sparse or outdated.

It still is, though it works somewhat seamlessly when installing with https://github.com/kata-containers/kata-containers/blob/main...

Though only one of the hypervisors works well.

Or even the other direction, upward toward full vms, or hybrid: https://github.com/kubevirt/kubevirt/blob/v1.4.0/docs/archit...

New cloud native projects: While working on the project, I had the opportunity to learn about other projects too. For example, Kubevirt, Kyverno, Clusterpedia, etc.

First, download virtctl for ARM: https://github.com/kubevirt/kubevirt/releases/tag/v1.1.0-alpha.0

The full list of changes can be found in the Release notes. There are performance and scalability benchmarks published for the v1.0 release.

If you're happy with k8s and longhorn, why add Proxmox as another layer underneath? Consider kubevirt ?

Have you looked at http://kubevirt.io/ ?

If the answer to "how do you run VMs" is "Kubernetes does it" then its about https://kubevirt.io/

We are even using Docker Hub to store and distribute VM images...

https://github.com/kubevirt/kubevirt/blob/main/containerimag...