3 ms·
So, it's not a hypervisor, KVM is the hypervisor, it's a management plane using perl and qemu (fixed it for you, you're right, libvirt isn't used, my bad) to do
by _joel 3y ago
So, it's not a hypervisor, KVM is the hypervisor, it's a management plane using perl and qemu (fixed it for you, you're right, libvirt isn't used, my bad) to do the same thing libvirt does.
Glad we cleared up that it's not a hypervisor though, KVM is the hypervisor, whatever glue that sits between them (be it perl/qemu or libvirt). Promox is still not a hypervisor.
- ar_lan 3y ago> So, it's not a hypervisor No. I disagree for reasons you refuse to respond to. > KVM is the hypervisor Yes I’ve said this since the beginning? > qemu Thanks for acknowledging you were a liar. > Proxmox is still not a hypervisor. I’ve already acknowledged why I see why you think this, because you want to strictly define the line at KVM. I, and many others, disagree with you. In fact, general Google consensus also disagrees with you. Please, change https://en.m.wikipedia.org/wiki/Proxmox_Virtual_Environment https://en.m.wikipedia.org/wiki/Proxmox_Virtual_Environment and https://en.m.wikipedia.org/wiki/Hypervisor https://en.m.wikipedia.org/wiki/Hypervisor if this is the biggest hill you must die on. Your weird pretense that Proxmox is not capable of deploying VMs is objectively wrong. How does it do it? Via KVM - an integral component of Proxmox. Since you’re a brick wall who can’t see nuance, understand conventional definitions, or even give the slightest amount of understanding to another point of view, then there’s no reason to keep talking with you.