Bug 1468016 - Switch to host-model as default CPU (for virt-manager and virt-install)
Summary: Switch to host-model as default CPU (for virt-manager and virt-install)
Keywords:
Status: CLOSED DUPLICATE of bug 1055002
Alias: None
Product: Virtualization Tools
Classification: Community
Component: virt-manager
Version: unspecified
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Cole Robinson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-05 19:07 UTC by Adam Williamson
Modified: 2017-07-10 23:47 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-10 23:47:47 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 870071 0 unspecified CLOSED Enabling <cpu mode="host-model"> gives a CPU config which doesn't match reality, causes kernel panics 2021-02-22 00:41:40 UTC

Internal Links: 870071

Description Adam Williamson 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 ***
Note You need to log in before you can comment on or make changes to this bug.