I can also verify this. I have a i7 cpu and if I "copy host cpu configuration" it sets it to "Westmere" but when running ps shows -cpu core2duo
If I run qemu-kvm with -cpu Westmere I get an error message:
Unable to find x86 CPU definition
Westmere is not a defined -cpu in qemu for F15. Available options for -cpu can be seen with qemu -cpu ?:
x86 [n270]
x86 [athlon]
x86 [pentium3]
x86 [pentium2]
x86 [pentium]
x86 [486]
x86 [coreduo]
x86 [kvm32]
x86 [qemu32]
x86 [kvm64]
x86 [core2duo]
x86 [phenom]
x86 [qemu64]
Though perhaps libvirt shouldn't try to set unsupported -cpu flags.
Description of problem: Configured Windows7 virtual machine with Westmere CPU in Virtual Machine Manager, but ps + iotop shows qemu always using the core2duo setting. Version-Release number of selected component (if applicable): qemu-kvm-0.14.0-7.fc15.x86_64 How reproducible: ALWAYS Steps to Reproduce: 1. Create Virtual Machine 2. Set CPU to Westmere (or other) 3. Run virtual machine 4. ps -ef | grep -i qemu 5. qemu-kvm shows cpu as core2duo instead of Westmere. Actual results: core2duo as qemu-kvm flag Expected results: Westmere as qemu-kvm flag Additional info: Output from PS: qemu 19566 1 25 00:03 ? 00:05:02 /usr/bin/qemu-kvm -S -M pc-0.14 -cpu core2duo Output from /etc/libvirt/qemu/Windoz7.xml <cpu match='exact'> <model>Westmere</model> <vendor>Intel</vendor> <feature policy='require' name='tm2'/> <feature policy='require' name='est'/> <feature policy='require' name='monitor'/> <feature policy='require' name='ss'/> <feature policy='require' name='vme'/> <feature policy='require' name='rdtscp'/> <feature policy='require' name='ht'/> <feature policy='require' name='ds'/> <feature policy='require' name='pbe'/> <feature policy='require' name='tm'/> <feature policy='require' name='vmx'/> <feature policy='require' name='ds_cpl'/> <feature policy='require' name='xtpr'/> <feature policy='require' name='acpi'/> </cpu>