(Edit 2019: This post is no longer accurate. virt-manager 2.0 and later uses
<cpu mode="host-model"/> by default as the host-model issues were fixed with sufficiently new libvirt and qemu. host-model and host-passthrough are nearly functionally equivalent as well so use of host-passthrough is less compelling.)
I described virt-manager's CPU model default in this post. In that post I explained the difficulties of using either of the libvirt options for mirroring the host CPU:
<cpu mode="host-model"/> still has operational issues, and
<cpu mode="host-passthrough"/> isn't recommended for use with libvirt over supportability concerns.
Unfortunately since writing that post the situation hasn't improved any, and since host-passthrough is the only reliably way to expose the full capabilities of the host CPU to the VM, users regularly want to enable it. This is particularly apparent if trying to do nested virt, which often doesn't work on Intel CPUs unless host-passthrough is used.
However we don't explicitly expose this option in virt-manager since it's not generally recommended for libvirt usage. You can however still enable it in virt-manager:
- Navigate to VM Details->CPU
- Enter host-passthrough in the CPU model field
- Click Apply