User:Egberts/Drafts/Virt-manager

The virt-manager application is a Article description::desktop user interface for management of virtual machines and containers through libvirt library.

Virt-manager shows all domains as running or inactive, presents performance data and utilization statistics. Virt-manager enable the easy creation of new domains, storage, network connections. Virt-manager also can reallocate host resources amongst the guest domain.

Overview

 * Firstly, virt-manager is a front-end to QEMU.
 * virt-manager can create/delete/maintain an instance of many virtual machine (VM).
 * virt-manager can start/stop a VM or a container.
 * virt-manager can mount a CD-ROM ISO image.
 * virt-manager can create different networking connections for the guest OS in VM to use.
 * virt-manager can create bridges, MACVLAN, static netdev, and NAT'd IP interface.
 * virt-manager can create/delete/maintain storage pools using many different filesystems such as directory, direct hard drive, gluster, iSCSI, LVM, multi-path devices, netfs, SCSI, RADOS/Ceph, and Sheepdog.

BIOS/UEFI
Verify that the host hardware has the needed virtualization support, issue the following command:

The vmx or svm CPU flag should be red highlighted and available.

And file must exist as well.

Kernel
The following kernel config is recommended by the libvirt installer (source?).

USE_EXPAND
Additional ebuild configuration frobs are provided as the USE_EXPAND variables QEMU_USER_TARGETS and QEMU_SOFTMMU_TARGETS. See for a list of all the available targets (there are a heck of a lot of them; most of them are very obscure and may be ignored; leaving these variables at their default values will disable almost everything which is probably just fine for most users).

For each target specified, a qemu executable will be built. A  target is the standard qemu use-case of emulating an entire system (like VirtualBox or VMWare, but with optional support for emulating CPU hardware along with peripherals). targets execute user-mode code only; the (somewhat shockingly ambitious) purpose of these targets is to "magically" allow importing user-space linux ELF binaries from a different architecture into the native system (that is, they are like multilib, without the awkward need for a software stack or CPU capable of running it).

In order to enable QEMU_USER_TARGETS and QEMU_SOFTMMU_TARGETS we can edit the variables globally in, i.e.:

Or, the file(s) can be modified. Two equivalent syntaxes are available: traditional USE flag syntax, i.e.:

Another alternative is to use the newer sexy USE_EXPAND -specific syntax:

Additional software
The requires the  package. See User:Egberts/libvirt for installation.

Checking Domain
Guest domains maintained by can be checked by doing:

Checking Networking
Network interfaces maintained by can be checked by running:

Checking Storage Pools
Storage pools maintained by can be checked by executing:

Checking Some Command I Cannot Recall
In case the mind slips, the group of -related options can be obtained by doing:

Then you can add the option for more detailed options specific to, for example, the  command:

== Troubleshooting TBS