On Proxmox ... On Mon, Dec 2, 2019 at 12:19 PM Fabian Thorns <[email protected]> wrote:
> ... it seems that Xen becomes less and less relevant while Qemu/KVM is > almost entirely used through other > means (libvirt, proxmox, ...), so testing their specific options and > configuration knobs might be arguable. > I'm a bit ignorant here on Proxmox, so I'm hoping someone can educate me. It's difficult to find 'technical internals' on it from Google searches, and I just lack enterprise experience with it. I know people use libvirt to name the 'tooling' -- especially GUIs and frameworks -- like virt-manager and those things that come out of the libvirt project. But does Proxmox still not just use libvirtd services -- and that 'tooling-support' -- to access KVM and other, libvirtd supported HyperVisors? Or does it use a completely different library and support? I'm not talking the GUI, but for setting up everything from KVM to network to storage? I ask because oVirt (Upstream, Downstream: Red Hat [Enterprise] Virtualization, RH[E]V) is using libvirtd (and RH[E]V only supports KVM), and other facilities (lots more), but not the libvirt 'end-user tooling,' like the virt-manager GUI. oVirt has its own, generic framework. So to me, that sounds like the same as Proxmox. Now I understand Proxmox also supports things outside of libvirtd facilities, including for LXC et al., that oVirt (or RH[E]V for that matter) never did (largely because the libvirtd facilities never did containers correctly, despite attempts to 'adapt' it). But it seems it's not so much libvirt v. Proxmox, but libvirtd w/o the libvirt 'end-user tooling,' same as oVirt. Which brings me back to focusing on the 'technical commonalities,' like libvirtd, how it sets up network, storage, etc... with QEMU, and the "non-GUI" *d/*ctl*/cmd tooling (e.g., udev, systemd, journald, NetworkManager, firewalld, et al.). Again, I'm very ignorant of Proxmox 'internals,' so I'm openly asking people to educate me. I'm trying to understand how Proxmox uses KVM, if it's not via libvirtd (note the 'd') and related support, like oVirt leverages libvirtd too, but *not* the libvirt 'end-user tooling.' - bjs
_______________________________________________ lpi-examdev mailing list [email protected] https://list.lpi.org/mailman/listinfo/lpi-examdev
