diff options
| author | Dayle Parker <dayleparker@redhat.com> | 2013-05-27 17:20:40 +1000 |
|---|---|---|
| committer | Dayle Parker <dayleparker@redhat.com> | 2013-05-27 17:20:40 +1000 |
| commit | 9fe22e3a649188dab9177e7565ee27db2a80228d (patch) | |
| tree | ae76c97613edf25da72ca07cbdca64e7f1dafbfc | |
| parent | 23900bc4dce2ef83df047a529a2b728c3d527f13 (diff) | |
| download | virtualization-getting-started-guide-9fe22e3a649188dab9177e7565ee27db2a80228d.tar.gz virtualization-getting-started-guide-9fe22e3a649188dab9177e7565ee27db2a80228d.tar.xz virtualization-getting-started-guide-9fe22e3a649188dab9177e7565ee27db2a80228d.zip | |
Revised CPU Models section according to SME feedback
| -rw-r--r-- | en-US/Products.xml | 33 | ||||
| -rw-r--r-- | en-US/Revision_History.xml | 16 |
2 files changed, 43 insertions, 6 deletions
diff --git a/en-US/Products.xml b/en-US/Products.xml index 9f4b374..cf5f137 100644 --- a/en-US/Products.xml +++ b/en-US/Products.xml @@ -510,8 +510,29 @@ </section> <section id="para-CPU_Models"> - <title>Guest CPU models</title> + <title>CPU models</title> <para> + CPU models define which host CPU features are available to + the guest operating system. <application>qemu-kvm</application> + and <application>libvirt</application> contain definitions for a + number of current processor models, allowing users to enable + features that are available only in newer CPU models. + The CPU feature set available to guests depends on + support in the host CPU kernel. The <application>qemu-kvm</application> + code must also allow the feature to be enabled. + </para> + <para> + To safely migrate virtual machines between hosts with different CPU + feature sets, <application>qemu-kvm</application> does not expose all CPU features + from the host CPU to guest operating systems by default. Instead, CPU features are + exposed to virtual machines based on the chosen CPU model. + </para> + <para> + It is also possible to enable or disable specific CPU features in a virtual machine's + XML configuration. However, it is safer to use predefined CPU models, as incorrect + configuration can cause compatibility issues with the guest operating system. + </para> + <!-- WAS: Historically, CPU model definitions were hard-coded in <application>qemu</application>. This method of defining CPU models was inflexible, and made it difficult to create virtual CPUs with feature sets @@ -526,13 +547,13 @@ 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. - </para> -<!-- <note> + </para>--> + <note> <para> - For more information on guest CPU models, refer to the <citetitle>Fedora Virtualization Deployment Guide</citetitle>. + For more information on CPU model availability and configuration, refer + to the <citetitle>Fedora Virtualization Deployment and Administration Guide</citetitle>. </para> - </note>--> - + </note> </section> </section> diff --git a/en-US/Revision_History.xml b/en-US/Revision_History.xml index 82d34f4..62b87dd 100644 --- a/en-US/Revision_History.xml +++ b/en-US/Revision_History.xml @@ -9,6 +9,22 @@ <revhistory> <!--EDIT MY REVNUMBER AND DESCRIPTION AT RELEASE TIME FOR MAJOR REVISION--> <revision> + <revnumber>1.0-09</revnumber> + <date>Monday May 27, 2013</date> + <author> + <firstname>Dayle</firstname> + <surname>Parker</surname> + <email>dayleparker@redhat.com</email> + </author> + <revdescription> + <simplelist> + <member>Updated CPU Models section based on SME feedback.</member> + <member>Added Virtio-RNG description to Para-virtualized Devices section.</member> + <member>Revised Para-virtualized Devices section based on SME feedback.</member> + </simplelist> + </revdescription> + </revision> + <revision> <revnumber>1.0-08</revnumber> <date>Thursday May 9, 2013</date> <author> |