Linux Virtualization Concepts: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 61: Line 61:


The storage for virtual machines is abstracted from the physical storage attached to the host. The storage is attached to the virtual machine using [[Virtualization_Concepts#Paravirtualized_Devices|paravirtualized]] or [[Virtualization_Concepts#Emulated_Devices|emulated]] block device drivers.
The storage for virtual machines is abstracted from the physical storage attached to the host. The storage is attached to the virtual machine using [[Virtualization_Concepts#Paravirtualized_Devices|paravirtualized]] or [[Virtualization_Concepts#Emulated_Devices|emulated]] block device drivers.
==Storage Pool==
{{External|[https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Virtualization_Deployment_and_Administration_Guide/chap-Storage_pools.html RHEL 7 Virtualization Administration Guide - Storage Pools]}}
==Storage Volume==


=Networking and Virtualization=
=Networking and Virtualization=

Revision as of 23:05, 23 June 2017

External

Internal

Generic Virtualization Concepts

Virtualization Concepts

Virtualization Solutions from Red Hat

RHEL 7 includes a hypervisor and a number of virtualization tools, which allows running guest operating systems, so it can function as a virtualization platform. However, the solution supports a limited number of guests per host and a limited range of guest types. Red Hat Virtualization is an enterprise virtualization solution based on the KVM technology, offering more features than Red Hat Enterprise Linux. Red Hat OpenStack Platform support OpenStack clouds.

KVM (Kernel-based Virtual Machine)

KVM is a hypervisor that only runs on systems with hardware supporting virtualization extensions. It is built into the standard RHEL 7 kernel, and it can run Linux, Windows, Solaris and BSD guests. KVM is integrated with the Quick Emulator (QEMU). KVM is managed with the libvirt API. The virtual machines are executed as multi-threaded Linux processes controlled by tools built in top of libvirt. KVM supports overcommitting, kernel same-page merging (KSM), disk I/O throttling, automatic NUMA balancing and virtual CPU hot add.

Xen

Xen can do full virtualization on systems that support virtualization extensions, but can also work as hypervisor on the machines that don't.

Quick Emulator (QEMU)

QEMU Guest Agent

The QEMU guest agent runs on the guest operating system and makes it possible for the host machine to issue commands to the guest operating system.

RHEL 7 Virtualization Administration Guide - QEMU guest agent

libvirt

libvirt is a package providing a hypervisor-independent C-based API that can be used to manage KVM as well as Xen. libvirt's clients are the virtualization management tools. The management tools do not need to be on the same physical machine as the machines on which the hosts are running.

libvirt provides access to management of virtual machines on a host. The API can be used to provision, create, modify, monitor, control, migrate and stop virtual machines. Resources such as CPUs, memory, storage, networking and non-uniform memory access (NUMA) partitions can be listed with libvirt. libvirt delegates management operations to the hypervisor, so only operations supported by the hypervisor can be performed with libvirt.

virsh, the primary command-line virtualization management tool, is baed on libvirt.

virtio

virtio is a package that provides KVM hypervisor-specific code, and exposes paravirtualized devices to the guest operating system. virtio is a layer sitting between the hypervisor and the guest. All virtio devices have two parts: the host device and the guest driver. The paravirtualized device drivers allow the guest operating system to access the corresponding physical device installed on the host system, and they must be installed on the guest operating system. Examples of paravirtualized devices: the paravirtualized network device virtio-net, the paravirtualized block device (virtio-blk), which is a high-performance virtual storage device supported by the hypervisor, the paravirtualized controller device (virtio-scsi), and others (clock, virtio-serrial, virtio-balloon, virtio-rng, QXL graphic card)

RHEL 7 Virtualization Administration Guide - Paravirtualized virtio Drivers

Also see paravirtualization and paravirtualized devices.

KVM and Physically Shared Devices

Also see physically shared devices.

Storage and Virtualization

The storage for virtual machines is abstracted from the physical storage attached to the host. The storage is attached to the virtual machine using paravirtualized or emulated block device drivers.

Storage Pool

RHEL 7 Virtualization Administration Guide - Storage Pools

Storage Volume

Networking and Virtualization

Security and Virtualization

KVM virtual machines use SELinux and sVirt to enforce security.

sVirt

sVirt is a technology included in RHEL 7 to integrate SELinux and virtualization. It applies Mandatory Access Control (MAC) to improve security when using virtual machines.

Steal Time

"Steal time" is the percentage of time a virtual CPU waits for real CPU while the hypervisor is servicing another virtual processor.

A high value means the physical CPU is overcommitted and more physical CPU should be allocated to the environment - or the VM should be moved on a different physical server. The steal time is reported by vmstat st.

RHEL 7 Virtualization Resource Limits

RHEL capabilities and limits
RHEL KVM virtualization capabilities and limits