In case anybody else wondered VMM = Virtual Machine Monitor.
Thank God this VMM is written in Rust, otherwise I would be very skeptical. I don't care about features or purpose or technical advantages, give me Rust or give me death.
Cargo.lock has 8750 lines. Is that normal for something like this?
For comparison, QEMU basically just needs glibc, glib and zlib for basic functionality.
How does this relate/compare to CloudHypervisor, another Rust based VMM that has been around for couple of years
Slides from Linux Plumbers talk about OpenHCL: https://lpc.events/event/18/contributions/1956/attachments/1...
Half the user guide is empty.
I want to understand what communication channel(s) it has from guest to host. It's not clear from the cut-and-paste support described in the VNC section of the manual, how this works and what other functionality might be supported.
Rust was something i thought was a cute little language years ago, much like i thought python was. I didn't pay attention for like 2 years and it feels likes it's everywhere and everything.
Time to learn.
it's written in rust is the only thing worth mentioning about it? congratulations on writing a thing that does something, i guess
A very interesting project. If I understand correctly it’s being used for Azure infrastructure.
A New Virtual Machine Monitor for Windows and Linux that happens to be written in Rust
VMM == Virtual Machine Monitor, "such as Hyper-V, QEMU, VirtualBox".
Nice! Would be pretty cool if this supported bhyve on FreeBSD.
[flagged]
Note this “disclaimer” in the guide:
> In recent years, development efforts in the OpenVMM project have primarily focused on OpenHCL (AKA: OpenVMM as a paravisor).
> As a result, not a lot of "polish" has gone into making the experience of running OpenVMM in traditional host contexts particularly "pleasant".
> This lack of polish manifests in several ways, including but not limited to: […]
> • No API or feature-set stability guarantees whatsoever.
https://github.com/microsoft/openvmm/blob/main/Guide/src/use...