QEMU

QEMU (Quick EMUlator) is Article description::a generic, open source hardware emulator and virtualization suite. Often it is used in conjunction with acceleration in the form of a Type-I hypervisor such as KVM (Kernel-based Virtual Machine) or Xen. If no accelerator is used, QEMU will run entirely in user-space using its built in binary translator TCG (Tiny Code Generator). Using QEMU without an accelerator is relatively inefficient and slow.

BIOS and UEFI firmware
In order to utilize KVM either Vt-x or AMD-V must be supported by the processor. Vt-x or AMD-V are Intel and AMD's respective technologies for permitting multiple operating systems to concurrently execute operations on the processors.

To inspect hardware for visualization support issue the following command:

For a period manufacturers were shipping with virtualization turned off by default in the system BIOS. Note that changing this feature in the BIOS may actually require full removal of power from the system to take effect. If restarting the system does not work try shutting down, unplugging the system and pressing the power button in an unplugged state to discharge any residual energy from the power supply unit (PSU). Reapply power to the system to verify success.

If KVM support is available there should be a "kvm" device listed at. This will take effect after the system has booted to a KVM enabled kernel.

Kernel
Activate the following kernel options:

Needed for  USE flag (recommend):

Needed for 802.1d Ethernet bridging:

USE flag is needed for file capabilities support:

When using the ext4 filesystem, enable the  USE flag if stats support is needed:

USE flags
Review the possible USE flags for QEMU:

USE_EXPAND
See for a list of possible values for QEMU_USER_TARGETS and QEMU_SOFTMMU_TARGETS.

For each target specified, a qemu executable will be built. Normally, a  target will work;   targets execute user-mode code only - i.e. the goal is to execute a single ELF binary from a different architecture, rather than an entire OS.

In order to enable QEMU_USER_TARGETS and QEMU_SOFTMMU_TARGETS you have to edit the file.

Otherwise you can always edit the file.

Emerge
After reviewing and adding any desired USE flags, emerge :

Networking
Basic networking support can be configured "out of the box" by creating a vlan with the following options.

A more advanced networking concept is outlined below, which enables guest access to an external network and also works with both wired and wireless adapters on the host. If desired, a DHCP server can also be setup on the host to allow for dynamic guest IP configurations. There are many different tutorials available online to further understand these concepts.

Required packages
This example networking configuration needs some extra software installed:

Creating TUN/TAP device
This allows the guest to communicate with the bridge. QEMU's default group is, ensure that the correct group is given permissions to control the TAP. Enabling promiscuous mode for the adapter might be unnecessary.

Create network bridge
Creating a network bridge seems necessary, even if only 1 guest is configured. Create the bridge and add each TAP to it. Spanning tree protocol is disabled because there is only 1 bridge.

Packet forwarding and NAT
Allows for proper packet routing (be sure to replace  with an appropriate network interface name):

Guest configuration
The following should be added to the configuration:

or, with QEMU 2.12.0 or newer:

After starting the guest, the IP should be configured to be on the vlan and the gateway should be the IP given to the bridge. The exact process will vary based on OS.

IPv6
For IPv6 networking see the IPv6 subarticle.

Permissions
In order to run a KVM accelerated virtual machine without logging as root, add normal users to the  group. Replace  in the example command below with the appropriate user(s):

Front ends
To make life easier, there are multiple user-friendly front ends to QEMU:

virt-manager
To run as a normal user, after emerging, ensure they are in the libvirt group:

Uncomment the following lines from the libvirtd configuration file:

Be sure to have the user log out then log in again for the new group settings to be applied.

Issue the following command to restart the libvirtd service under OpenRC:

Issue the following command to restart the libvirtd service under Systemd:

should now be launchable as a regular user.

Usage
The following sub-articles provide instructions on QEMU usage:


 * Usage options - Contains common options used with QEMU.
 * Linux guest - Describes the configuration steps needed to setup Linux to run on QEMU.
 * Windows guest - Describes the configuration steps needed to setup Windows to run on QEMU.
 * OS2WarpV3 guest - Describes the configuration steps needed to setup OS2WarpVs=3 to run on QEMU.

"kvm: already loaded the other module"
Sometimes during the early boot splash the error message "kvm: already loaded the other module" can be seen. This message indicates both the Intel and the AMD kernel virtual machine settings have been enabled in the kernel. To fix this, enable as a module or disable either the Intel or AMD KVM option specific to the system's processor in the kernel configuration. For example, if the system has an Intel processor enable the Intel KVM, then make sure the AMD KVM is set as a module (M) or is disabled (N). The relevant options to enable or disable can be found in the kernel's file via the CONFIG_KVM_INTEL and CONFIG_KVM_AMD variables or in the configuration section above.

Creating TUN/TAP device - No such file or directory
Sometimes this error can occur if TUN/TAP support cannot be found in the kernel. To solve this, try loading the driver:

If that works, add this to a file in /etc/modules-load.d/ to load on startup:

External resources

 * http://www.linux-kvm.org/page/KvmOnGentoo - The Gentoo article on the KVM wiki
 * http://wiki.qemu.org/Main_Page - The Official QEMU wiki
 * http://www.tuxradar.com/content/howto-linux-and-windows-virtualization-kvm-and-qemu - A TuxRadar howto.