it manages images, storage, starting and stopping VMs, etc.). it emulates the underlying hardware and handles communications with the host), libvirtd manages virtual machines ( i.e. VMM doesn’t communicate directly with QEMU, so it’s not a QEMU client. They also run in separate processes.Īs explained here, libvirtd is a dæmon, which might qualify as a server process in your terminology. The GUI is similar to Virtual Machine Manager, and the VM engine is similar to KVM/QEMU. The GUI you’re presumably used to is one component VMs can be run separately and managed using other tools, e.g. VirtualBox is split into multiple components. VMM and the VMs it manages run in separate processes in QEMU’s case, VMM and QEMU communicate using Unix domain sockets (under /var/lib/libvirt/qemu). VMM isn’t a hypervisor itself, it’s a GUI used to manage virtual machines (and LXC containers). The virt-manager application is a desktop user interface for managing virtual machines through libvirt. I’m not sure why the Wikipedia article links that particular phrase to the hypervisor article the description of Virtual Machine Manager on its own web site is more accurate:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |