2 ms·
> The latter 2 usages are pretty much the same. Only if you ignore most of reality, sure.
by msla 1y ago
> The latter 2 usages are pretty much the same.
Only if you ignore most of reality, sure.
- lproven 1y ago> Only if you ignore most of reality, sure. No, not really. Hypervisor VM: emulates a virtual computer with virtual, emulated hardware, but a simulated version of the same CPU as the host, allowing 1 OS to run under another. E.g. Xen, VMware, KVM, bhyve Bytecode VM: emulates a partial virtual environment, with an emulated CPU and some form of conversion or translation from virtual environment to the underlying real API and real OS, allowing programs to execute on radically different OSes on different CPUs. E.g. JVM, MoarVM, Parrot VM, Dis in Inferno Emulator VM: emulates a virtual computer with virtual, emulated hardware, including a virtual CPU. E.g. MESS, RetroVM, ZesaruX Container: emulates an OS from userland down, but shares the same OS kernel across instances. E.g. Docker, LXC, LXD, Incus, FreeBSD jails, Solaris Zones
- msla 11mo agoSo you can't tell the difference between a hypervisor and a bytecode interpreter. OK.