diff options
Diffstat (limited to 'en-US/What_Is_It.xml')
| -rw-r--r-- | en-US/What_Is_It.xml | 22 |
1 files changed, 11 insertions, 11 deletions
diff --git a/en-US/What_Is_It.xml b/en-US/What_Is_It.xml index 756e53d..241f354 100644 --- a/en-US/What_Is_It.xml +++ b/en-US/What_Is_It.xml @@ -13,7 +13,7 @@ <varlistentry><term><emphasis role="strong">Full virtualization</emphasis></term> <listitem> <para> - 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 <firstterm>virtual machine</firstterm>, 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 Fedora. + 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 <firstterm>virtual machine</firstterm>, that allows guest operating systems to run without modifications. The guest operating system and any applications on the guest virtual machine 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 Fedora. </para> </listitem> </varlistentry> @@ -32,16 +32,16 @@ </listitem> </varlistentry> </variablelist> - <note> +<!-- <note> Include once VDAG is published. <para> - For more information and detailed instructions on guest installation, refer to the <citetitle>Fedora Virtualization Deployment Guide</citetitle>. + For more information and detailed instructions on guest installation, refer to the <citetitle>Fedora Virtualization Deployment and Administration Guide</citetitle>. </para> - </note> + </note>--> </section> <section id="sec-migration"> <title>Migration</title> <para> - <firstterm>Migration</firstterm> 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. + <firstterm>Migration</firstterm> describes the process of moving a guest 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. </para> <variablelist> <title>Migration Types</title> @@ -49,7 +49,7 @@ <term><emphasis role="strong">Offline migration</emphasis></term> <listitem> <para> - 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. + An offline migration suspends the guest virtual machine, and then moves an image of the virtual machine's memory to the destination host. The virtual machine is then resumed on the destination host and the memory used by the virtual machine on the source host is freed. </para> </listitem> </varlistentry> @@ -57,7 +57,7 @@ <term><emphasis role="strong">Live migration</emphasis></term> <listitem> <para> - Live migration is the process of migrating an active guest from one physical host to another. + Live migration is the process of migrating an active virtual machine from one physical host to another. </para> </listitem> </varlistentry> @@ -70,7 +70,7 @@ <term><emphasis role="strong">Load balancing</emphasis></term> <listitem> <para> - When a host machine is overloaded, one or many of its virtual machines could be migrated to other hosts. + When a host machine is overloaded, one or many of its virtual machines could be migrated to other hosts using live migration. </para> </listitem> </varlistentry> @@ -102,11 +102,11 @@ <para> 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 <application>libvirt</application>-managed storage pools for shared storage. </para> - <note> +<!-- <note> <para> - For more information on migration, refer to the <citetitle>Fedora Virtualization Administration Guide</citetitle>. + For more information on migration, refer to the <citetitle>Fedora Virtualization Depolyment and Administration Guide</citetitle>. </para> - </note> + </note>--> </section> </section> <!-- <section id="Virtualized_to_virtualized"> |