Bug 1468016

Summary: Switch to host-model as default CPU (for virt-manager and virt-install)
Product: [Community] Virtualization Tools Reporter: Adam Williamson (Red Hat non-Fedora) <awilliam>
Component: virt-managerAssignee: Cole Robinson <crobinso>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: berrange, crobinso, ehabkost, gscrivan, rbalakri
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-07-10 23:47:47 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Adam Williamson (Red Hat non-Fedora) 2017-07-05 19:07:56 UTC 
virtManager/config.py has this little stanza in `get_default_cpu_setting`, the method for returning the 'default' CPU model:

        if for_cpu and ret == CPU.SPECIAL_MODE_HOST_MODEL:
            # host-model has known issues, so use our 'copy cpu'
            # behavior until host-model does what we need
            ret = CPU.SPECIAL_MODE_HOST_COPY

I believe the 'known issues' referred to there are those documented in https://bugzilla.redhat.com/show_bug.cgi?id=870071 , which is closed from libvirt 3.2.0 onwards.

Perhaps this workaround should now be removed, or made conditional on libvirt < 3.2.0, at this point?

Note: I'll be opening a similar issue on Boxes, which acts similarly.
Comment 1 Cole Robinson 2017-07-10 23:47:47 UTC 

*** This bug has been marked as a duplicate of bug 1055002 ***