5 ms·
They only mention KVM, however KVM is a kernel API and not a full hypervisor, and can't do half the things they claim it does (like support for certain disk ima
by homebrewer 2y ago
They only mention KVM, however KVM is a kernel API and not a full hypervisor, and can't do half the things they claim it does (like support for certain disk images). What hypervisor are they actually using, does anybody know? Probably qemu? It doesn't feel like a major enough company to be able to write its own like Google did.
- klooney 2y agoThey probably mean libvirtd/qemu, when people say "we used kvm" that's generally what they mean.
- freedomben 2y agoThey are most assuredly using qemu. It's been my experience that when most people say "KVM" they usually are referring to the whole libvirt ecosystem. I assume that's the case here. I think of it very analogously to how people say "linux" to refer to a full OS/distro such as Fedora. Though "linux" is just a kernel, it's become common parlance.
- blueflow 2y agoKVM is not only the kernel side - the userspace side of KVM was implemented in a fork of qemu. That fork later got merged into mainline qemu, so qemu is the "original" implementation of a KVM hypervisor.
- deleted 2y ago[deleted]
- bertman 2y agoNetcup seem to use qemu[0], which is what Anexia will also use according to OP's article [0]https://old.reddit.com/r/VPS/comments/1ghz4fd/i_know_contabo_uses_proxmox_what_does_hetzner_and/lv2amg7/ https://old.reddit.com/r/VPS/comments/1ghz4fd/i_know_contabo...