by g0xA52A2A on 10/17/24, 5:42 AM with 118 comments
by robjwells on 10/17/24, 10:23 AM
> 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...
by tonyedgecombe on 10/17/24, 10:01 AM
by ericyd on 10/17/24, 1:05 PM
by Vogtinator on 10/17/24, 1:26 PM
For comparison, QEMU basically just needs glibc, glib and zlib for basic functionality.
by zokier on 10/17/24, 10:20 AM
by rwmj on 10/17/24, 11:59 AM
by efitz on 10/17/24, 3:13 PM
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.
by AlfredBarnes on 10/17/24, 1:18 PM
Time to learn.
by vrighter on 10/17/24, 1:32 PM
by kosolam on 10/17/24, 9:17 AM
by Dowwie on 10/17/24, 2:06 PM
by hollerith on 10/17/24, 2:44 PM
by _0xdd on 10/17/24, 4:53 PM
by low_tech_love on 10/17/24, 9:40 AM