AMD Joins The Cloud Hypervisor Project Started By Intel

[phoronix]

Phoronix: AMD Joins The Cloud Hypervisor Project Started By Intel

Over the past three years one of Intel's many promising open-source software projects has been the Rust-written Cloud Hypervisor. Cloud Hypervisor started as just a modern, security-focused, cloud-centric Rust VMM hypervisor for modern hardware/software. It began as just one of many open-source software projects at Intel but last year was folded into the Linux Foundation umbrella while Intel continues to be a major contributor to the project. Coming as a bit of a surprise today is AMD announcing they have joined the Cloud Hypervisor project...

https://www.phoronix.com/news/AMD-Cloud-Hypervisor

[NeoMorpheus]

Careful AMD, could be a trap! :-)

[Jabberwocky]

Why "The Cloud Hypervisor Project" over existing projects like Qemu or Xen?

Where is this project used?

[CommunityMember]

Why "The Cloud Hypervisor Project" over existing projects like Qemu or Xen?

Qeum is very powerful, including processor and peripheral emulation. It is (sort of) the kitchen sink of VMMs, and when you need it, you need it. But it is overkill for the way most VMs are run in the cloud (or even on many desktops) today and with complexity comes development overheads and bugs including security. The Cloud Hypervisor only supports the native processor architecture and virtio devices (with a few emulated devices), which covers the majority of real world use cases. The result is a smaller execution footprint and a smaller (security related) target surface of the VMM. It also written in rust, so a class of potential security bugs should not be possible.

[Quackdoc]

Qeum is very powerful, including processor and peripheral emulation. It is (sort of) the kitchen sink of VMMs, and when you need it, you need it. But it is overkill for the way most VMs are run in the cloud (or even on many desktops) today and with complexity comes development overheads and bugs including security. The Cloud Hypervisor only supports the native processor architecture and virtio devices (with a few emulated devices), which covers the majority of real world use cases. The result is a smaller execution footprint and a smaller (security related) target surface of the VMM. It also written in rust, so a class of potential security bugs should not be possible.

to sum it up, simple is better.

Qemu is as simple as it can be for the needs it has, (being a quick emulator for a lot of systems)