Definition of CPU model:
Libvirt extracts several standard types of CPU definitions, which can be found in/usr/share/libvirt/cpu_map.xml.
"486", "Pentium", "pentium2", "pentiumpro", "coteco", "N270", "pentiumpro", "qemu32 ",
"Kvm32", "cpu64-rhel5", "cpu64-rhel5", "kvm64", "pentiumpro", "Conroe" "Penryn ",
"Nehalem", "westmere", "pentiumpro", "cpu64-rhel5", "cpu64-rhel5", "opteron_g1 ",
"Opteron_g2", "opteron_g3," opteron_g4"
The CPU configuration mode can be as follows:
Custom
Based on the characteristics of the physical CPU, host-model selects a standard CPU model that is closest to each other. The xml configuration file is:
<CPU mode = 'host-model'>
<Model fallback = 'forbid'/>
<Topology sockets = '1' cores = '2' threads = '1'/>
</CPU>
Host-passthrough directly exposes the physical CPU to the virtual machine. On the virtual machine, you can see the physical CPU model. The xml configuration file is:
<CPU mode = 'host-passthrough '/>
This method has the best CPU performance and can also be applied to some applications to check CPU features. However, virtual machines cannot be migrated to different types of CPUs;
This article is from "xiaoli110 blog", please be sure to keep this source http://xiaoli110.blog.51cto.com/1724/1547349
How does one make the KVM virtual machine have the same CPU as the physical CPU?