Merge "changes to section_hypervisor_kvm"

This commit is contained in:
Jenkins 2014-06-05 21:49:14 +00:00 committed by Gerrit Code Review
commit c22c354047

View File

@ -118,15 +118,15 @@ virt_type = kvm</programlisting>
<literal>cpu_mode=host-passthrough</literal>, libvirt tells KVM to pass through
the host CPU with no modifications. The difference to host-model, instead of just
matching feature flags, every last detail of the host CPU is matched. This gives
absolutely best performance, and can be important to some apps which check low level
CPU details, but it comes at a cost with respect to migration: the guest can only be
migrated to an exactly matching host CPU.</para>
the best performance, and can be important to some apps which check low level
CPU details, but it comes at a cost with respect to migration. The guest can only be
migrated to a matching host CPU.</para>
</simplesect>
<simplesect>
<title>Custom</title>
<para>If your <filename>nova.conf</filename> file contains
<literal>cpu_mode=custom</literal>, you can explicitly specify one of the
supported named model using the cpu_model configuration option. For example, to
supported named models using the cpu_model configuration option. For example, to
configure the KVM guests to expose Nehalem CPUs, your <filename>nova.conf</filename>
file should contain:</para>
<programlisting language="ini">[libvirt]
@ -146,7 +146,7 @@ cpu_model = Nehalem</programlisting>
<para>Use guest agents to enable optional access between compute nodes and guests through a
socket, using the QMP protocol.</para>
<para>To enable this feature, you must set <literal>hw_qemu_guest_agent=yes</literal> as a
metadata parameter on the image you wish to use to create guest-agent-capable instances
metadata parameter on the image you wish to use to create the guest-agent-capable instances
from. You can explicitly disable the feature by setting
<literal>hw_qemu_guest_agent=no</literal> in the image metadata.</para>
</section>
@ -165,7 +165,7 @@ cpu_model = Nehalem</programlisting>
<screen><computeroutput>libvirtError: internal error no supported architecture for os type 'hvm'</computeroutput></screen>
<para>This message indicates that the KVM kernel modules were not loaded.</para>
<para>If you cannot start VMs after installation without rebooting, the permissions might
not be correct. This can happen if you load the KVM module before you install
not be set correctly. This can happen if you load the KVM module before you install
<systemitem class="service">nova-compute</systemitem>. To check whether the group is
set to <systemitem>kvm</systemitem>, run:</para>
<screen><prompt>#</prompt> <userinput>ls -l /dev/kvm</userinput></screen>