From b5ac9d00e1b5725b946d50fb32b5f948331f554b Mon Sep 17 00:00:00 2001 From: Dayle Parker Date: Wed, 27 Jun 2012 11:20:56 +1000 Subject: Initial import from Red Hat SVN. --- beta.cfg | 10 + en-US/Advantages.xml | 154 ++++++++ en-US/Author_Group.xml | 14 + en-US/Book_Info.xml | 33 ++ en-US/Introduction.xml | 75 ++++ en-US/Preface.xml | 13 + en-US/Products.xml | 512 +++++++++++++++++++++++++ en-US/Revision_History.xml | 441 +++++++++++++++++++++ en-US/Terms.xml | 15 + en-US/Tools.xml | 399 +++++++++++++++++++ en-US/Virtualization_Getting_Started_Guide.ent | 4 + en-US/Virtualization_Getting_Started_Guide.xml | 16 + en-US/What_Is_It.xml | 103 +++++ en-US/images/icon.svg | 19 + publican.cfg | 9 + zanata.xml | 86 +++++ 16 files changed, 1903 insertions(+) create mode 100644 beta.cfg create mode 100644 en-US/Advantages.xml create mode 100644 en-US/Author_Group.xml create mode 100644 en-US/Book_Info.xml create mode 100644 en-US/Introduction.xml create mode 100644 en-US/Preface.xml create mode 100644 en-US/Products.xml create mode 100644 en-US/Revision_History.xml create mode 100644 en-US/Terms.xml create mode 100644 en-US/Tools.xml create mode 100644 en-US/Virtualization_Getting_Started_Guide.ent create mode 100644 en-US/Virtualization_Getting_Started_Guide.xml create mode 100644 en-US/What_Is_It.xml create mode 100644 en-US/images/icon.svg create mode 100644 publican.cfg create mode 100644 zanata.xml diff --git a/beta.cfg b/beta.cfg new file mode 100644 index 0000000..e480a78 --- /dev/null +++ b/beta.cfg @@ -0,0 +1,10 @@ +# Config::Simple 4.59 +# Mon Apr 4 13:11:07 2011 + +xml_lang: en-US +type: Book +brand: RedHat +condition: beta +git_branch: docs-rhel-6 +version: 6-Beta +web_version_label: "6.x Beta" diff --git a/en-US/Advantages.xml b/en-US/Advantages.xml new file mode 100644 index 0000000..62f7a41 --- /dev/null +++ b/en-US/Advantages.xml @@ -0,0 +1,154 @@ + + + + Advantages and misconceptions of virtualization + + + There are many advantages to virtualization and perhaps an equal amount of misconceptions surrounding it. This chapter will explore these points. + + +
+ Virtualization costs + + + A common misconception is that virtualization is too expensive to justify the change. Virtualization can be expensive to introduce but often it saves money in the long term. It is important to perform a Return on Investment (ROI) analysis to determine the best use of virtualization in your environment. Consider the following benefits: + + + + + Less power + + + Using virtualization negates much of the need for multiple physical platforms. This equates to less power being drawn for machine operation and cooling, resulting in reduced energy costs. The initial cost of purchasing multiple physical platforms, combined with the machines' power consumption and required cooling, is drastically cut by using virtualization. + + + + + + Less maintenance + + + Provided adequate planning is performed before migrating physical systems to virtualized ones, less time is spent maintaining them. This means less money being spent on parts and labor. + + + + + + Extended life for installed software + + + Older versions of software may not run on newer, bare metal machines directly. However, by running the older software virtually on a larger, faster system, the life of the software may be extended while taking advantage of the performance from the newer system. + + + + + + + + + Predictable costs + + + A Red Hat Enterprise Linux subscription provides support for virtualization at the normal fixed rate, making it easy to predict costs. + + + + + + Less space + + + Consolidating servers onto fewer machines means less physical space is required. This means the space normally occupied by server hardware can be used for other purposes. + + + + + +
+ +
+ Virtualization learning curve + + + A misconception exists that virtualization is difficult to learn. In truth, virtualization is no more difficult or easy to learn than any new process. The skills required for managing and supporting a physical environment are easily transferable to a virtual one. Virtual environments function similarly to their physical counterparts, ensuring the learning curve remains a slight one. + + +
+ +
+ Performance + + + On older virtualization versions that supported only a single CPU, virtual machines experienced noticeable performance limitations. This created a long-lasting misconception that virtualization solutions are slow. This is no longer the case; advances in technology allow virtual machines to run at much faster speeds than previously. + + +
+ +
+ Disaster recovery + + + Disaster recovery is quicker and easier when the systems are virtualized. On a physical system, if something serious goes wrong, a complete re-install of the operating system is usually required, resulting in hours of recovery time. However, if the systems are virtualized this is much faster due to migration ability. If the requirements for live migration are followed, virtual machines can be restarted on another host, and the longest possible delay would be in restoring guest data. Also, because each of the virtualized systems are completely separate to each other, one system's downtime will not affect any others. + + +
+ +
+ Security + + + + A virtual machine uses SELinux and sVirt to improve security in virtualization. This section includes an overview of the security options available. + + +
+ Virtualization security features + + SELinux + SELinux was developed by the US National Security Agency and others to provide Mandatory Access Control (MAC) for Linux. Under control of SELinux, all processes and files are given what is known as a type, and access is limited by fine-grained controls. SELinux limits the abilities of an attacker and works to prevent many common security exploits such as buffer overflow attacks and privilege escalation. + + SELinux strengthens the security model of Red Hat Enterprise Linux hosts and virtualized Red Hat Enterprise Linux guests. SELinux is configured and tested to work, by default, with all virtualization tools shipped with Red Hat Enterprise Linux 6. + + + For more information on SELinux, refer to the SELinux documentation at . For specific details on the relationship between SELinux and virtualization, refer to the Red Hat Enterprise Linux 6 Virtualization Administration Guide. + + + + sVirt + sVirt is a technology included in Red Hat Enterprise Linux 6 that integrates SELinux and virtualization. It applies Mandatory Access Control (MAC) to improve security when using virtual machines, and improves security and hardens the system against bugs in the hypervisor that might be used as an attack vector for the host or to another virtual machine. + + For more information on sVirt, refer to the Red Hat Enterprise Linux 6 Virtualization Administration Guide. +
+ +
+ +
+ Virtualization for servers and individuals + + + Virtualization is not just for servers, it can be useful for individuals as well. Desktop virtualization offers centralized management, an improved desktop solution, and better disaster recovery. Using connection software it is possible to connect to a desktop remotely. + + + + For servers, virtualization is not only for larger networks, but for any situation with two or more servers. It provides live migration, high availability, fault tolerance, and streamlined backups. + + +
+ + + + diff --git a/en-US/Author_Group.xml b/en-US/Author_Group.xml new file mode 100644 index 0000000..00a1e36 --- /dev/null +++ b/en-US/Author_Group.xml @@ -0,0 +1,14 @@ + + +%BOOK_ENTITIES; +]> + + + + Red Hat + Engineering Content Services + + + + diff --git a/en-US/Book_Info.xml b/en-US/Book_Info.xml new file mode 100644 index 0000000..181da45 --- /dev/null +++ b/en-US/Book_Info.xml @@ -0,0 +1,33 @@ + + +%BOOK_ENTITIES; +]> + + Virtualization Getting Started Guide + Virtualization Documentation + Red Hat Enterprise Linux + 6 + 6.3 Beta + 0.2 + 83 + + + The Red Hat Enterprise Linux Virtualization Getting Started Guide describes the basics of virtualization and the virtualization products and technologies that are available with Red Hat Enterprise Linux. + + + + Note: This document is under development, is subject to substantial change, and is provided only as a preview. +The included information and instructions should not be considered complete, and should be used with caution. + + + + + + + + + + + + diff --git a/en-US/Introduction.xml b/en-US/Introduction.xml new file mode 100644 index 0000000..69f698b --- /dev/null +++ b/en-US/Introduction.xml @@ -0,0 +1,75 @@ + + + + Introduction + + + The Virtualization Getting Started Guide introduces the basics of virtualization and assists with the navigation of other virtualization documentation and products that Red Hat provides. + + + + This guide also explains the advantages of virtualization and dispels some common myths that exist regarding virtualization. + + + +
+ Who should read this guide? + + This guide is designed for anyone wishing to understand the basics of virtualization, but may be of particular interest to: + + + + Those who are new to virtualization and seeking knowledge about the benefits offered. + + + + + + Those considering deployment of virtualized machines in their environment. + + + + + + Those looking for an overview of the virtualization technologies that Red Hat produces and supports. + + + + +
+ +
+ Red Hat Enterprise Virtualization (RHEV) + + Red Hat Enterprise Virtualization for Servers is an end-to-end virtualization solution that is designed to enable pervasive datacenter virtualization and significantly enhance capital and operational efficiency. Red Hat Enterprise Virtualization 3.0 introduces several new features, including desktop virtualization with the Red Hat Enterprise Virtualization for Desktop add-on subscription. + + + + With Red Hat Enterprise Virtualization for Desktops, complete desktop environments are hosted as virtual desktops on servers located in a centralized datacenter. + + + + Information on both these products can be found at . + + + + The full collection of Red Hat Enterprise Virtualization (RHEV) documentation can be found at . + + +In addition to the documentation for Red Hat Enterprise Virtualization products and this guide, the following titles cover virtualization with Red Hat Enterprise Linux: + + + + + Virtualization Host Configuration and Guest Installation Guide: This guide provides information on system requirements and restrictions, package details, host configuration and detailed instructions for installing different types of guests. + + + + + Virtualization Administration Guide: This guide provides information on best server practices, security, KVM, remote management of guests, KSM, administration tasks, storage, volumes, virt-manager, guest disk access with offline tools, virtual networking, and troubleshooting. + + + +
+ diff --git a/en-US/Preface.xml b/en-US/Preface.xml new file mode 100644 index 0000000..b380674 --- /dev/null +++ b/en-US/Preface.xml @@ -0,0 +1,13 @@ + + +%BOOK_ENTITIES; +]> + + Preface + + + + + + diff --git a/en-US/Products.xml b/en-US/Products.xml new file mode 100644 index 0000000..082a5f4 --- /dev/null +++ b/en-US/Products.xml @@ -0,0 +1,512 @@ + + + + Introduction to Red Hat virtualization products + This chapter introduces the various virtualization products available in Red Hat Enterprise Linux. +
+ KVM and virtualization in Red Hat Enterprise Linux + + What is KVM? + + KVM (Kernel-based Virtual Machine) is a full virtualization solution for Linux on AMD64 and Intel 64 hardware that is built into the standard Red Hat Enterprise Linux 6 kernel. It can run multiple, unmodified Windows and Linux guest operating systems. The KVM hypervisor in Red Hat Enterprise Linux is managed with the libvirt API and tools built for libvirt (such as virt-manager and virsh). Virtual machines are executed and run as multi-threaded Linux processes controlled by these tools. + + + + Overcommitting + + KVM hypervisor supports overcommitting of system resources. Overcommitting means allocating more virtualized CPUs or memory than the available resources on the system. Memory overcommitting allows hosts to utilize memory and virtual memory to increase guest densities. + + + + Overcommitting involves possible risks to system stability. For more information on overcommitting with KVM, and the precautions that should be taken, refer to the Red Hat Enterprise Linux 6 Virtualization Administration Guide. + + + Thin provisioning + + Thin provisioning allows the allocation of flexible storage and optimizes the available space for every guest. It gives the appearance that there is more physical storage on the guest than is actually available. This is not the same as overcommitting as this only pertains to storage and not CPUs or memory allocations. However, like overcommitting, the same warning applies. + + + + Thin provisioning involves possible risks to system stability. For more information on thin provisioning with KVM, and the precautions that should be taken, refer to the Red Hat Enterprise Linux 6 Virtualization Administration Guide. + + + KSM + + Kernel SamePage Merging (KSM), used by the KVM hypervisor, allows KVM guests to share identical memory pages. These shared pages are usually common libraries or other identical, high-use data. KSM allows for greater guest density of identical or similar guest operating systems by avoiding memory duplication. + + + + For more information on KSM, refer to the Red Hat Enterprise Linux 6 Virtualization Administration Guide. + + + KVM Guest VM Compatibility + To verify whether your processor supports the virtualization extensions and for information on enabling the virtualization extensions if they are disabled, refer to the Red Hat Enterprise Linux 6 Virtualization Administration Guide. + + + Red Hat Enterprise Linux 6 servers have certain support limits. + + + The following URLs explain the processor and memory amount limitations for Red Hat Enterprise Linux: + + + + For host systems: http://www.redhat.com/products/enterprise-linux/server/compare.html + + + For hypervisors: http://www.redhat.com/resourcelibrary/articles/virtualization-limits-rhel-hypervisors + + + + For a complete chart of supported operating systems and host and guest combinations refer to http://www.redhat.com/resourcelibrary/articles/enterprise-linux-virtualization-support. + +
+
+ libvirt and libvirt tools + The libvirt package is a hypervisor-independent virtualization API that is able to interact with the virtualization capabilities of a range of operating systems. + + The libvirt package provides: + + + A common, generic, and stable layer to securely manage virtual machines on a host. + + + + A common interface for managing local systems and networked hosts. + + + + All of the APIs required to provision, create, modify, monitor, control, migrate, and stop virtual machines, but only if the hypervisor supports these operations. Although multiple hosts may be accessed with libvirt simultaneously, the APIs are limited to single node operations. + + + + + The libvirt package is designed as a building block for higher level management tools and applications, for example, virt-manager and the virsh command line management tools. With the exception of migration capabilities, libvirt focuses on managing single hosts and provides APIs to enumerate, monitor and use the resources available on the managed node, including CPUs, memory, storage, networking and Non-Uniform Memory Access (NUMA) partitions. The management tools can be located on separate physical machines from the host using secure protocols. + + Red Hat Enterprise Linux 6 supports libvirt and included libvirt-based tools as its default method for virtualization management (as in Red Hat Enterprise Virtualization Management). + The libvirt package is available as free software under the GNU Lesser General Public License. The libvirt project aims to provide a long term stable C API to virtualization management tools, running on top of varying hypervisor technologies. The libvirt package supports Xen on Red Hat Enterprise Linux 5, and it supports KVM on both Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6. + + + virsh + + The virsh command-line tool is built on the libvirt management API and operates as an alternative to the graphical virt-manager application. The virsh command can be used in read-only mode by unprivileged users or, with root access, full administration functionality. The virsh command is ideal for scripting virtualization administration. + + + virt-manager + + virt-manager is a graphical desktop tool for managing virtual machines. It allows access to graphical guest consoles and can be used to perform virtualization administration, virtual machine creation, migration, and configuration tasks. The ability to view virtual machines, host statistics, device information and performance graphs is also provided. The local hypervisor and remote hypervisors can be managed through a single interface. + + + For more information on virt-manager, refer to the Red Hat Enterprise Linux 6 Virtualization Administration Guide. + +
+
+ Virtualized hardware devices + Virtualization on Red Hat Enterprise Linux 6 presents three distinct types of system devices to virtual machines. The three types include: + + + Emulated software devices + + + Para-virtualized devices + + + Physically shared devices + + + These hardware devices all appear as being physically attached to the virtual machine but the device drivers work in different ways. +
+ Virtualized and emulated devices + + KVM implements many core devices for virtual machines in software. These emulated hardware devices are crucial for virtualizing operating systems. + Emulated devices are virtual devices which exist entirely in software. + Emulated drivers may use either a physical device or a virtual software device. Emulated drivers are a translation layer between the virtual machine and the Linux kernel (which manages the source device). The device level instructions are completely translated by the KVM hypervisor. Any device, of the same type (storage, network, keyboard, and mouse) and recognized by the Linux kernel, may be used as the backing source device for the emulated drivers. + + Virtual CPUs (vCPUs) + + A host system can have up to 160 virtual CPUs (vCPUs) that can be presented to guests for their use, regardless of the number of host CPUs. + + + + Emulated graphics devices + Two emulated graphics devices are provided. These devices can be connected to with the SPICE (Simple Protocol for Independent Computing Environments) protocol or with VNC: + + + + A Cirrus CLGD 5446 PCI VGA card (using the cirrus device) + + + A standard VGA graphics card with Bochs VESA extensions (hardware level, including all non-standard modes) + + + + + Emulated system components + The following core system components are emulated to provide basic system functions: + + + + + + Intel i440FX host PCI bridge + + + PIIX3 PCI to ISA bridge + + + PS/2 mouse and keyboard + + + EvTouch USB Graphics Tablet + + + PCI UHCI USB controller and a virtualized USB hub + + + + Emulated serial ports + + + EHCI controller, virtualized USB storage and a USB mouse + + + + Emulated sound devices + + Red Hat Enterprise Linux 6.1 and above provides an emulated (Intel) HDA sound device, intel-hda. This device is supported on the following guest operating systems: + + + + + + Red Hat Enterprise Linux 6, for i386 and x86_64 architectures + + + + + Red Hat Enterprise Linux 5, for i386 and x86_64 architectures + + + + + Red Hat Enterprise Linux 4, for i386 and x86_64 architectures + + + + + + Windows 7, for i386 and x86_64 architectures + + + + + Windows 2008 R2, for the x86_64 architecture + + + + + The following two emulated sound devices are also available, but are not recommended due to compatibility issues with certain guest operating systems: + + + + ac97, an emulated Intel 82801AA AC97 Audio compatible sound card + + + es1370, an emulated ENSONIQ AudioPCI ES1370 sound card + + + + Emulated watchdog devices + Red Hat Enterprise Linux 6.0 and above provides two emulated watchdog devices. A watchdog can be used to automatically reboot a virtual machine when it becomes overloaded or unresponsive. + + + + The watchdog package must be installed on the guest. + + + The two devices available are: + + + + + i6300esb, an emulated Intel 6300 ESB PCI watchdog device. It is supported in guest operating system Red Hat Enterprise Linux versions 6.0 and above, and is the recommended device to use. + + + + + ib700, an emulated iBase 700 ISA watchdog device. The ib700 watchdog device is only supported in guests using Red Hat Enterprise Linux 6.2 and above. + + + + + Both watchdog devices are supported in i386 and x86_64 architectures for guest operating systems Red Hat Enterprise Linux 6.2 and above. + + + Emulated network devices + There are two emulated network devices available: + + + + The e1000 device emulates an Intel E1000 network adapter (Intel 82540EM, 82573L, 82544GC). + + + The rtl8139 device emulates a Realtek 8139 network adapter. + + + + + Emulated storage drivers + Storage devices and storage pools can use these emulated devices to attach storage devices to virtual machines. The guest uses an emulated storage driver to access the storage pool + + + Note that like all virtual devices, the storage drivers are not storage devices. The drivers are used to attach a backing storage device, file or storage pool volume to a virtual machine. The backing storage device can be any supported type of storage device, file, or storage pool volume. + + + + The emulated IDE driver + + + KVM provides two emulated PCI IDE interfaces. An emulated IDE driver can be used to attach any combination of up to four virtualized IDE hard disks or virtualized IDE CD-ROM drives to each virtual machine. Emulated IDE driver is also used for virtualized CD-ROM and DVD-ROM drives. + + + + The emulated floppy disk drive driver + + The emulated floppy disk drive driver is used for creating virtualized floppy drives. + + + +
+
+ Para-virtualized devices + + + Para-virtualized devices are drivers for virtual devices that increase the I/O performance of virtual machines. + + + Para-virtualized devices decrease I/O latency and increase I/O throughput to near bare-metal levels. It is recommended to use the para-virtualized drivers for virtual machines running I/O intensive applications. + + The para-virtualized devices must be installed on the guest operating system. By default, the para-virtualized drivers are included in Red Hat Enterprise Linux 4.7 and newer, Red Hat Enterprise Linux 5.4 and newer and Red Hat Enterprise Linux 6.0 and newer. The para-virtualized drivers must be manually installed on Windows guests. + For more information on using the para-virtualized drivers refer to the Red Hat Enterprise Linux 6 Virtualization Host Configuration and Guest Installation Guide. + + + Para-virtualized network driver (virtio-net) + The para-virtualized network driver is a Red Hat branded virtual network device. It can be used as the driver for existing network devices or new network devices for virtual machines. + + + Para-virtualized block driver (virtio-blk) + The para-virtualized block driver is a driver for all storage devices, is supported by the hypervisor, and is attached to the virtual machine (except for floppy disk drives, which must be emulated). + + + The para-virtualized clock + + Guests using the Time Stamp Counter (TSC) as a clock source may suffer timing issues. KVM works around hosts that do not have a constant Time Stamp Counter by providing guests with a para-virtualized clock. + + + The para-virtualized serial driver (virtio-serial) + The para-virtualized serial driver is a bytestream-oriented, character stream driver, and provides a simple communication interface between the host's user space and the guest's user space. + + + + The balloon driver (virtio-balloon) + The balloon driver can designate part of a virtual machine's RAM as not being used (a process known as balloon inflation), so that the memory can be freed for the host (or for other virtual machines on that host) to use. When the virtual machine needs the memory again, the balloon can be deflated and the host can distribute the RAM back to the virtual machine. + + + + +
+
+ Physical host devices + Certain hardware platforms allow virtual machines to directly access various hardware devices and components. This process in virtualization is known as device assignment. Device assignment is also known as passthrough. + + + PCI device assignment + The KVM hypervisor supports attaching PCI devices on the host system to virtual machines. PCI device assignment allows guests to have exclusive access to PCI devices for a range of tasks. It allows PCI devices to appear and behave as if they were physically attached to the guest operating system. + + + + Device assignment is supported on PCI Express devices, with the exception of graphics cards. Parallel PCI devices may be supported as assigned devices, but they have severe limitations due to security and system configuration conflicts. + + For more information on device assignment, refer to the Red Hat Enterprise Linux 6 Virtualization Host Configuration and Guest Installation Guide. + + + + USB passthrough + + The KVM hypervisor supports attaching USB devices on the host system to virtual machines. USB device assignment allows guests to have exclusive access to USB devices for a range of tasks. It allows USB devices to appear and behave as if they were physically attached to the virtual machine. + + + + + For more information on USB passthrough, refer to the Red Hat Enterprise Linux 6 Virtualization Administration Guide. + + + + + SR-IOV + + SR-IOV (Single Root I/O Virtualization) is a PCI Express standard that extends a single physical PCI function to share its PCI resources as separate, virtual functions (VFs). Each function is capable of being used by a different virtual machine via PCI device assignment. + + + + An SR-IOV capable PCI-e device, provides a Single Root Function (for example, a single Ethernet port) and presents multiple, separate virtual devices as unique PCI device functions. Each virtual device may have its own unique PCI configuration space, memory-mapped registers, and individual MSI-based interrupts. + For more information on SR-IOV, refer to the Red Hat Enterprise Linux 6 Virtualization Host Configuration and Guest Installation Guide. + + NPIV + N_Port ID Virtualization (NPIV) is a functionality available with some Fibre Channel devices. NPIV shares a single physical N_Port as multiple N_Port IDs. NPIV provides similar functionality for Fibre Channel Host Bus Adapters (HBAs) that SR-IOV provides for PCIe interfaces. With NPIV, virtual machines can be provided with a virtual Fibre Channel initiator to Storage Area Networks (SANs).NPIV can provide high density virtualized environments with enterprise-level storage solutions. + For more information on NPIV, refer to the Red Hat Enterprise Linux 6 Virtualization Administration Guide. +
+ +
+ Guest CPU models + + + Historically, CPU model definitions were hard-coded in + qemu. This method of defining CPU models was + inflexible, and made it difficult to create virtual CPUs with feature sets + that matched existing physical CPUs. Typically, users modified a basic CPU + model definition with feature flags in order to provide the CPU + characteristics required by a virtual machine. Unless these feature sets were carefully + controlled, safe migration — which requires feature sets between current and + prospective hosts to match — was difficult to support. + + + qemu-kvm has now replaced most hard-wired definitions + with configuration file based CPU model definitions. Definitions for a number + of current processor models are now included by default, allowing users to specify + features more accurately and migrate more safely. + + + + A list of supported CPU models can be viewed with the + /usr/libexec/qemu-kvm -cpu ?model command. This command outputs + the name used to select the CPU model at the command line, + and a model identifier that corresponds to a commercial instance of that processor + class. The CPU models that Red Hat Enterprise Linux supports can be found in the qemu-kvm Whitelist chapter in the Virtualization Administration Guide. + + + + Configuration details for all of these CPU models can be output with the + /usr/libexec/qemu-kvm -cpu ?dump command, but they are also stored in the + /usr/share/qemu-kvm/cpu-model/cpu-x86_64.conf file + by default. Each CPU model definition begins with [cpudef], as shown: + + [cpudef] + name = "Nehalem" + level = "2" + vendor = "GenuineIntel" + family = "6" + model = "26" + stepping = "3" + feature_edx = "sse2 sse fxsr mmx clflush pse36 pat cmov mca \ + pge mtrr sep apic cx8 mce pae msr tsc pse de fpu" + feature_ecx = "popcnt x2apic sse4.2 sse4.1 cx16 ssse3 sse3" + extfeature_edx = "i64 syscall xd" + extfeature_ecx = "lahf_lm" + xlevel = "0x8000000A" + model_id = "Intel Core i7 9xx (Nehalem Class Core i7)" + + + The four CPUID fields, feature_edx, feature_ecx, + extfeature_edx and extfeature_ecx, accept + named flag values from the corresponding feature sets listed by the + /usr/libexec/qemu-kvm -cpu ?cpuid command, as shown: + + # /usr/libexec/qemu-kvm -cpu ?cpuid +Recognized CPUID flags: + f_edx: pbe ia64 tm ht ss sse2 sse fxsr mmx acpi ds clflush pn \ + pse36 pat cmov mca pge mtrr sep apic cx8 mce pae msr tsc \ + pse de vme fpu + f_ecx: hypervisor avx osxsave xsave aes popcnt movbe x2apic \ + sse4.2|sse4_2 sse4.1|sse4_1 dca pdcm xtpr cx16 fma cid \ + ssse3 tm2 est smx vmx ds_cpl monitor dtes64 pclmuldq \ + pni|sse3 + extf_edx: 3dnow 3dnowext lm rdtscp pdpe1gb fxsr_opt fxsr mmx \ + mmxext nx pse36 pat cmov mca pge mtrr syscall apic cx8 \ + mce pae msr tsc pse de vme fpu + extf_ecx: nodeid_msr cvt16 fma4 wdt skinit xop ibs osvw \ + 3dnowprefetch misalignsse sse4a abm cr8legacy extapic svm \ + cmp_legacy lahf_lm + + These feature sets are described in greater detail in the appropriate Intel + and AMD specifications. + + + It is important to use the check flag to verify that all + configured features are available. + + # /usr/libexec/qemu-kvm -cpu Nehalem,check +warning: host cpuid 0000_0001 lacks requested flag 'sse4.2|sse4_2' [0x00100000] +warning: host cpuid 0000_0001 lacks requested flag 'popcnt' [0x00800000] + + If a defined feature is not available, those features will fail silently + by default. + + + +
+
+
+ Storage + Storage for virtual machines is abstracted from the physical storage used by the virtual machine. It is attached to the virtual machine using the para-virtualized or emulated block device drivers. +
+ Storage pools + + A storage pool is a file, directory, or storage device managed by libvirt for the purpose of providing storage to virtual machines. Storage pools are divided into storage volumes that store virtual machine images or are attached to virtual machines as additional storage. Multiple guests can share the same storage pool, allowing for better allocation of storage resources. Refer to the Red Hat Enterprise Linux 6 Virtualization Administration Guide for more information. + + + + + Local storage pools + + Local storage pools are directly attached to the host server. They include local directories, directly attached disks, physical partitions, and LVM volume groups on local devices. Local storage pools are useful for development, testing and small deployments that do not require migration or large numbers of virtual machines. Local storage pools may not be suitable for many production environments as they do not support live migration. + + + + Networked (shared) storage pools + + Networked storage pools include storage devices shared over a network using standard protocols. Networked storage is required for migrating virtual machines between hosts. Networked storage pools are managed by libvirt. + + + + Storage Volumes + Storage pools are further divided into storage volumes. Storage volumes are an abstraction of physical partitions, LVM logical volumes, file-based disk images and other storage types handled by libvirt. Storage volumes are presented to virtualized guests as local storage devices regardless of the underlying hardware. + + For more information on storage and virtualization refer to the Red Hat Enterprise Linux 6 Virtualization Administration Guide. + +
+
+ diff --git a/en-US/Revision_History.xml b/en-US/Revision_History.xml new file mode 100644 index 0000000..f134d8a --- /dev/null +++ b/en-US/Revision_History.xml @@ -0,0 +1,441 @@ + + +%BOOK_ENTITIES; +]> + + Revision History + + + + + 0.2-83 + Mon June 18 2012 + + Dayle + Parker + dayleparker@redhat.com + + + + Version for 6.3 GA release + + + + + 0.2-82 + Mon June 18 2012 + + Dayle + Parker + dayleparker@redhat.com + + + + Corrected "64 vCPUs" to "160 vCPUs" for BZ#832415. + + + + + 0.2-80 + Tues June 12 2012 + + Dayle + Parker + dayleparker@redhat.com + + + + Clarified emulated watchdog device section for BZ#827307. + + + + + 0.2-78 + Fri June 8 2012 + + Dayle + Parker + dayleparker@redhat.com + + + + Corrected typos and markup for BZ#827305. + General corrections made to Chapter 4 BZ#827307. + + + + + 0.2-73 + Mon 23 April 2012 + + Laura + Novich + lnovich@redhat.com + + + + Corrections made to chapter 5 (BZ#798108). + + + + + 0.2-72 + Mon 23 April 2012 + + Laura + Novich + lnovich@redhat.com + + + + Corrections made to chapter 4 (BZ#798106). + + + + + 0.2-71 + Thur 19 April 2012 + + Laura + Novich + lnovich@redhat.com + + + + Corrections made to chapter 5 (BZ#798108). + + + + + 0.2-69 + Wed 18 April 2012 + + Laura + Novich + lnovich@redhat.com + + + + Corrections made to chapter 4 (BZ#798106). + + + + + 0.2-68 + Tue 17 April 2012 + + Dayle + Parker + dayleparker@redhat.com + + + + Corrected terminology to "virtual machine" where needed (BZ#798063). + + + + + 0.2-64 + Mon 2 April 2012 + + Laura + Novich + lnovich@redhat.com + + + + BZ#800401 Corrections to Chapter 2 + + + + + 0.2-61 + Fri 30 March 2012 + + Dayle + Parker + dayleparker@redhat.com + + + + Made corrections in Chapter 3: Advantages (BZ#800409). + Adjusted terms to "virtual machine" and "virtualized guest" where appropriate; corrected outdated link in 4.1; corrected terms in Emulated network devices (from drivers) in (BZ#798063). + + + + + 0.2-52 + Wed 11 January 2012 + + Jacquelynn + East + jeast@redhat.com + + + + BZ#772859 clarified acronym. + + + + + 0.2-51 + Fri 04 November 2011 + + Jacquelynn + East + jeast@redhat.com + + + + BZ#750969 minor typos. + + + + + 0.2-47 + Fri 14 October 2011 + + Jacquelynn + East + jeast@redhat.com + + + + BZ#744156 add paragraph about emulated watchdogs. + + + + + 0.2-45 + Sun 18 September 2011 + + Scott + Radvan + sradvan@redhat.com + + + + Minor wording issues. + + + + + 0.2-44 + Fri 16 September 2011 + + Jacquelynn + East + jeast@redhat.com + + + + BZ#734614 + + + + + 0.2-43 + Fri 16 September 2011 + + Jacquelynn + East + jeast@redhat.com + + + + BZ#734618 minor edit + + + + + + 0.2-37 + Fri 2 September 2011 + + Jacquelynn + East + jeast@redhat.com + + + + BZ#734619, BZ#734614 + + + + + + 0.2-34 + Thu 1 September 2011 + + Jacquelynn + East + jeast@redhat.com + + + + BZ#734619, BZ#734511, BZ#734618, BZ#734616, BZ#715476, BZ#734613 + + + + + + 0.2-33 + Wed 31 August 2011 + + Jacquelynn + East + jeast@redhat.com + + + + BZ#734618, BZ#734613, BZ#734619 + + + + + + 0.2-34 + Thu 25 August 2011 + + Scott + Radvan + sradvan@redhat.com + + + + 6.2 development. + + + + + + + + + + 0.2-24 + Fri July 29 2011 + + Jacquelynn + East + jeast@redhat.com + + + + Extensive edits, combine security section into advantages + + + + + + + 0.2-22 + Wed July 27 2011 + + Jacquelynn + East + jeast@redhat.com + + + + Advantages chapter completed BZ#715476 + + + + + + 0.2-20 + Tue July 26 2011 + + Jacquelynn + East + jeast@redhat.com + + + + More of the Advantages draft + + + + + + 0.2-17 + Mon July 25 2011 + + Jacquelynn + East + jeast@redhat.com + + + + Minor edits for BZ#715473 and BZ#715474 + + + + + + 0.2-15 + Mon July 25 2011 + + Jacquelynn + East + jeast@redhat.com + + + + Chapter 4 draft BZ#715476 + + + + + + 0.2-4 + Thu June 23 2011 + + Jacquelynn + East + jeast@redhat.com + + + + Completed chapter 1 + + + + + + + + + 0.1-01 + Wed May 4 2011 + + Scott + Radvan + sradvan@redhat.com + + + + Arrange basic layout and book infrastructure. Import introductory text. + + + + + 0.0-01 + Wed May 4 2011 + + Scott + Radvan + sradvan@redhat.com + + + + Initial creation of book by Publican. + + + + + + + diff --git a/en-US/Terms.xml b/en-US/Terms.xml new file mode 100644 index 0000000..aac3529 --- /dev/null +++ b/en-US/Terms.xml @@ -0,0 +1,15 @@ + + + + Common virtualization terms + This chapter explains some basic Virtualization terms. + + + KVM - KVM is.. + + + V2V - V2V is.. + + + diff --git a/en-US/Tools.xml b/en-US/Tools.xml new file mode 100644 index 0000000..36a4e9e --- /dev/null +++ b/en-US/Tools.xml @@ -0,0 +1,399 @@ + + +%BOOK_ENTITIES; +]> + + + Virtualization Tools + + + Read this chapter for an introduction to the many tools available to assist + with virtualization. + + +
+ <command>virsh</command> + + virsh is a command line interface (CLI) tool for managing guests and the hypervisor. The virsh command-line tool is built on the libvirt management API and operates as an alternative to the qemu-kvm command and the graphical virt-manager application. The virsh command can be used in read-only mode by unprivileged users or, with root access, full administration functionality. The virsh command is ideal for scripting virtualization administration. In addition the virsh tool is a main management interface for virsh guest domains and can be used to create, pause, and shut down domains, as well as list current domains. This tool is installed as part of the libvirt-client package. + + + + Refer to the Red Hat Enterprise Linux 6 Virtualization Administration Guide for more information about managing virtual machines with virsh. + + +
+ +
+ <command>virt-manager</command> + + A light-weight graphical tool for managing virtual machines. It provides the ability + to control the life cycle of existing machines, provision new machines, + manage virtual networks, access the graphical console of virtual + machines, and view performance statistics. This tool ships in its own + package called virt-manager. + + + + Refer to the Red Hat Enterprise Linux 6 Virtualization Administration Guide for more information about managing virtual machines with virt-manager. + + +
+ +
+ <command>virt-install</command> + + A command line tool to provision new virtual machines. It supports both + text-based and graphical installations, using serial console, SDL, SPICE, or VNC client/server pair graphics. Installation media can be local, + or exist remotely on an NFS, HTTP, or FTP server. The tool can also be + configured to run unattended and kickstart the guest when installation is + complete, allowing for easy automation of installation. This tool is + installed as part of the python-virtinst package. + + + + Refer to the Red Hat Enterprise Linux 6 Virtualization Host Configuration and Guest Installation Guide for more information about virt-install. + + +
+ +
+ <command>guestfish</command> + + A command line tool for examining and modifying the file systems of + the host. This tool uses libguestfs and + exposes all functionality provided by the guestfs API. + This tool ships in its own package entitled guestfish. + + + Refer to the Red Hat Enterprise Linux 6 Virtualization Administration Guide for more information about guestfish. + + + + Using guestfish on running virtual machines can + cause disk-image corruption. Use the guestfish command with the (read-only) + option if the disk image is being used by a running virtual machine. + + +
+ + +
+ Other useful tools + The following tools are used to access a virtual machine's disk via the host. The guest's disk is usually accessed directly via the disk-image file located on the host. However it is sometimes possible to gain access via the libvirt domain. The commands that follow are part of the libvirt domain and are used to gain access to the guest's disk image. + + + + guestmount + + + A command line tool used to mount virtual machine file systems and disk + images on the host machine. This tool is installed as part of the libguestfs-mount package. + + + + Using guestmount in read/write mode to access a disk that is currently being used by a guest can cause the disk to become corrupted. Do not use guestmount in read/write mode on live virtual machines. Use the guestmount command with the (read-only) + option if the disk image is being used. + + + + + + virt-cat + + + A command line tool that can be used to quickly view the contents of + one or more files in a specified virtual machine's disk or disk image. This + tool is installed as part of the libguestfs-tools + package + + + + Using virt-cat on running virtual machines can + cause disk corruption in the virtual machine. Do not use + virt-cat command on a running virtual machine. + + + + + + + + virt-df + + + A command line tool used to show the actual physical disk usage of + virtual machines. Similar to the command line tool df. + Note that this tool does not work across remote connections. It is + installed as part of the libguestfs-tools package. + + + + + virt-edit + + + A command line tool used to edit files that exist on a specified virtual + machine. This tool is installed as part of the + libguestfs-tools package. + + + + Using virt-edit on live virtual machines can + cause disk corruption in the virtual machine. + Although the virt-edit command will try to prevent users from editing + files on live virtual machines, it is not guaranteed to catch all instances. + Therefore, do not use virt-edit on a live virtual machine. + + + + + + virt-filesystems + + + A command line tool used to discover file systems, partitions, logical + volumes and their sizes in a disk image or virtual machine. One common + use is in shell scripts, to iterate over all file systems in a disk + image. This tool is installed as part of the + libguestfs-tools package. + + + This tool replaces virt-list-filesystems and + virt-list-partitions. + + + + + virt-inspector + + + A command line tool that can examine a virtual machine or disk image to + determine the version of its operating system and other information. + It can also produce XML output, which can be piped into other programs. + Note that virt-inspector can only inspect one domain + at a time. This tool is installed as part of the + libguestfs-tools package. + + + + + virt-inspector2 + + + An alternative tool to virt-inspector, written in C. This tool is installed as part of the libguestfs-tools package. + + + + + virt-ls + + + A command line tool that lists files and directories inside a virtual + machine. This tool is installed as part of the + libguestfs-tools package. + + + + + virt-make-fs + + + A command line tool for creating a file system based on a tar archive + or files in a directory. It is similar to tools like + mkisofs and mksquashfs, but it + can create common file system types such as ext2, ext3 and NTFS, and + the size of the file system created can be equal to or greater than the + size of the files it is based on. This tool is provided as part of the + libguestfs-tools package. + + + + + + virt-rescue + + + A command line tool that provides a rescue shell and some simple + recovery tools for unbootable virtual machines and disk images. It can + be run on any virtual machine known to libvirt, or directly on disk + images. This tool is installed as part of the + libguestfs-tools package. + + + + Using virt-rescue on running virtual machines can + cause disk corruption in the virtual machine. + virt-rescue attempts to prevent its own use on + running virtual machines, but cannot catch all cases. + + + Using the command with the (read-only) option + will not cause disk corruption, but may give strange or inconsistent + results. It is better to avoid using virt-rescue + on a running virtual machine. + + + + + + virt-resize + + + A command line tool to resize virtual machine disks, and resize or + delete any partitions on a virtual machine disk. It works by copying the guest image and leaving the original disk image untouched. This tool is installed as part of the + libguestfs-tools package. + + + + Using virt-resize on running virtual machines can + give inconsistent results. It is best to shut down virtual machines + before attempting to resize them. + + + + + + virt-tar + + + + A command line archive tool for downloading and uploading parts of a + virtual machine's file system. This tool is commonly used for making backups, + uploading data, reviewing guest activity, and fixing or customizing + guests. This tool is installed as part of the + libguestfs-tools package. + + + + Using virt-tar with the + (upload) option on running virtual machines can cause disk corruption + in the virtual machine. virt-tar attempts to + prevent its own use on running virtual machines, but cannot catch + all cases. + + + Using virt-tar with the + (extract) option on running virtual machines will not cause disk + corruption, but may give strange or inconsistent results. It is best + to shut down virtual machines before attempting to extract files from + them. + + + + + + virt-top + + + A command line utility similar to top, which shows + stats related to virtualized domains. This tool ships in its own package: + virt-top. + + + + + virt-v2v + + + A graphical tool to convert virtual machines from Xen and VMware hypervisors + to run on KVM. This tool ships in its own package: + virt-v2v. + + + + + virt-viewer + + + A minimal tool for displaying the graphical console of a virtual machine via + the VNC and SPICE protocols. This tool ships in its own package: + virt-viewer. + + + + + virt-what + + + A shell script that detects whether a program is running in a virtual machine. + This tool ships in its own package: virt-what. + + + + + virt-who + + + The virt-who package is a Red Hat Enterprise Linux host agent that queries libvirt for guest UUIDs. It then passes that data to the local entitlement server for the purposes of issuing certificates. This tool ships in its own package: virt-who. + + + + + virt-win-reg + + + A command line tool to export and merge Windows Registry entries from a + Windows guest, and perform simple Registry operations. This tool is installed + as part of the libguestfs-tools package. + + + + Using virt-win-reg on running virtual machines will + cause irreversible disk corruption in the virtual machine. + virt-win-reg attempts to prevent its own use on + running virtual machines, but cannot catch all cases. + + + + + Modifying the Windows Registry is an inherently risky operation, as the + format is deliberately obscure and undocumented. Changes to the registry + can leave the system unbootable, so ensure you have a reliable backup + before you use the option. + + + + + + virt-xml-validate + + + A command line tool to validate libvirt XML files for compliance with the + published schema. This tool is installed as part of the + libvirt-client package. + + + + +
+ + diff --git a/en-US/Virtualization_Getting_Started_Guide.ent b/en-US/Virtualization_Getting_Started_Guide.ent new file mode 100644 index 0000000..1fa555c --- /dev/null +++ b/en-US/Virtualization_Getting_Started_Guide.ent @@ -0,0 +1,4 @@ + + + + diff --git a/en-US/Virtualization_Getting_Started_Guide.xml b/en-US/Virtualization_Getting_Started_Guide.xml new file mode 100644 index 0000000..a8b702c --- /dev/null +++ b/en-US/Virtualization_Getting_Started_Guide.xml @@ -0,0 +1,16 @@ + + +%BOOK_ENTITIES; +]> + + + + + + + + + + + diff --git a/en-US/What_Is_It.xml b/en-US/What_Is_It.xml new file mode 100644 index 0000000..c1764d6 --- /dev/null +++ b/en-US/What_Is_It.xml @@ -0,0 +1,103 @@ + + + + What is virtualization and migration? + In this chapter, terms related to virtualization and migration will be discussed. +
+ What is virtualization? + Virtualization is a broad computing term used for running software, usually multiple operating systems, concurrently and in isolation from other programs on a single system. Most existing implementations of virtualization use a hypervisor, a software layer or subsystem that controls hardware and provides guest operating systems with access to underlying hardware. The hypervisor allows multiple operating systems, called guests, to run on the same physical system by offering virtualized hardware to the guest operating system. There are various methods for virtualizing operating systems: + + Full virtualization + + + Full virtualization uses the hardware features of the processor to provide guests with total abstraction of the underlying physical system. This creates a new virtual system, called a virtual machine, that allows guest operating systems to run without modifications. The guest operating system and any applications on the guest are unaware of their virtualized environment and run normally. Hardware-assisted virtualization is the technique used for full virtualization with KVM (Kernel-based Virtual Machine) in Red Hat Enterprise Linux. + + + + Para-virtualization + + + Para-virtualization employs a collection of software and data structures that are presented to the virtualized guest, requiring software modifications in the guest to use the para-virtualized environment. Para-virtualization can encompass the entire kernel, as is the case for Xen para-virtualized guests, or drivers that virtualize I/O devices. + + + + Software virtualization (or emulation) + + + Software virtualization uses slower binary translation and other emulation techniques to run unmodified operating systems. Software virtualization is unsupported by Red Hat Enterprise Linux. + + + + + + + For more information and detailed instructions on guest installation, refer to the Red Hat Enterprise Linux 6 Virtualization Host Configuration and Guest Installation Guide. + +
+
+ Migration + Migration describes the process of moving a virtual machine from one host to another. This is possible because guests are running in a virtualized environment instead of directly on the hardware. There are two ways to migrate a virtual machine: live and offline. + + Migration Types + + Offline migration + + + An offline migration suspends the guest, and then moves an image of the guest's memory to the destination host. The guest is then resumed on the destination host and the memory used by the guest on the source host is freed. + + + + + Live migration + + + Live migration is the process of migrating an active guest from one physical host to another. + + + + +
+ Benefits of migrating virtual machines + Migration is useful for: + + Load balancing + + When a host machine is overloaded, one or many of its virtual machines could be migrated to other hosts. + + + Upgrading or making changes to the host + + When the need arises to upgrade, add, or remove hardware devices on one host, virtual machines can be safely relocated to other hosts. This means that guests do not experience any downtime due to changes that are made to any of the hosts. + + + Energy saving + + Virtual machines can be redistributed to other hosts and the unloaded host systems can be powered off to save energy and cut costs in low usage periods. + + + Geographic migration + Virtual machines can be moved to another physical location for lower latency or for other special circumstances. + + + + + It is important to understand that the migration process moves the virtual machine's memory, and from Red Hat Enterprise Linux 6.3, the disk volume associated with the virtual machine is also migrated. This process is done using Live Block Migration — information about this can be found in the Red Hat Enterprise Linux 6 Virtualization Administration Guide. + + + Shared, networked storage must be used for storing guest images to be migrated. Without shared storage, migration is not possible. It is recommended to use libvirt-managed storage pools for shared storage. + + + For more information on migration refer to the Red Hat Enterprise Linux 6 Virtualization Administration Guide. + +
+
+
+ Virtualized to virtualized migration (V2V) + Red Hat Enterprise Linux 6 provides tools for converting virtual machines from other types of hypervisors to KVM. The virt-v2v tool converts and imports virtual machines from Xen, other versions of KVM, and VMware ESX. + + For more information on V2V, refer to the Red Hat Enterprise Linux 6 V2V Guide. + +
+ + diff --git a/en-US/images/icon.svg b/en-US/images/icon.svg new file mode 100644 index 0000000..b2f16d0 --- /dev/null +++ b/en-US/images/icon.svg @@ -0,0 +1,19 @@ + + + + + + + + + + + + + + + + + + + diff --git a/publican.cfg b/publican.cfg new file mode 100644 index 0000000..53cd9df --- /dev/null +++ b/publican.cfg @@ -0,0 +1,9 @@ +# Config::Simple 4.59 +# Mon Apr 4 13:11:07 2011 + +xml_lang: en-US +type: Book +brand: RedHat +condition: ga +git_branch: docs-rhel-6 + diff --git a/zanata.xml b/zanata.xml new file mode 100644 index 0000000..8f53977 --- /dev/null +++ b/zanata.xml @@ -0,0 +1,86 @@ + + + https://translate.zanata.org/zanata/ + rhev-gsg + 2.2 + + + ar + as + bg + bn-IN + ca + cs + da + de-CH + de-DE + el + en-GB + es-ES + es-MX + fa + fi + fr + gu + he + hi + hr + hu + id + is + it + ja + kn + ko + lv + ml + mr + ms + nb + nl + or + pl + pt-PT + pt-BR + ru + si + sk + sr-Cyrl + sr-Latn + sv + ta-IN + te + th + tr + uk + zh-Hans-CN + zh-Hant-TW + af + am + az + bn-BD + cy + eo + et + eu + ga + gl + ka + lt + nn + ro + sl + sq + vi + ast + bs + nds + ky + la + mn + tl + xh + pa + + + -- cgit