RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1533415 - Libvirt may prefer $CPUModel over $CPUModel-IBRS when reporting host CPU model [rhel-7.3.z]
Summary: Libvirt may prefer $CPUModel over $CPUModel-IBRS when reporting host CPU mode...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.5
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: ---
Assignee: Jiri Denemark
QA Contact: Luyao Huang
URL:
Whiteboard:
Depends On: 1533125
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-11 10:04 UTC by Oneata Mircea Teodor
Modified: 2018-01-25 12:59 UTC (History)
9 users (show)

Fixed In Version: libvirt-2.0.0-10.el7_3.11
Doc Type: Bug Fix
Doc Text:
As a part of security update CVE-2017-5715, the libvirt service is expected to report whether the host CPU model was secured against the Kernel Side-channel Attacks exploit. However, in certain cases, libvirt incorrectly reported secured CPU models as unsecured. This problem has been fixed, and libvirt now reports the security status of the host CPU correctly.
Clone Of: 1533125
Environment:
Last Closed: 2018-01-25 12:59:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0188 0 normal SHIPPED_LIVE libvirt bug fix update 2018-01-25 17:26:08 UTC

Description Oneata Mircea Teodor 2018-01-11 10:04:02 UTC 
This bug has been copied from bug #1533125 and has been proposed to be backported to 7.3 z-stream (EUS).
Comment 5 Luyao Huang 2018-01-16 08:51:36 UTC 
Reproduce this issue on libvirt-2.0.0-10.el7_3.10.x86_64:

0. prepare a skylake cpu host which have update the microcode and can see the spec_ctrl in cpu flags:

# cat /proc/cpuinfo

flags		: ... spec_ctrl ibpb_support ...

1. change the skylake client cpu model number to match host cpu model in cpu_map.xml if needed (this help to reproduce this issue):

2. restart libvirtd and recheck host caps:

virsh # capabilities 
...
      <arch>x86_64</arch>
      <model>Skylake-Client</model>
...
      <feature name='spec-ctrl'/>
...

3. start a guest with host-model cpu and recheck qemu cmd line and xml:

# virsh dumpxml vm1 --update-cpu
...
  <cpu mode='host-model' match='exact'>
    <model fallback='forbid'>Skylake-Client</model>
    <vendor>Intel</vendor>
...
    <feature policy='require' name='spec-ctrl'/>
...

# ps aux|grep qemu
 -cpu Skylake-Client, ...+spec-ctrl...


And verify this bug with libvirt-2.0.0-10.el7_3.11.x86_64:

1. change the skylake client cpu model number to match host cpu model in cpu_map.xml if needed (this help to reproduce this issue):

2. restart libvirtd and recheck host caps:
 
virsh # capabilities 
<capabilities>

...
      <model>Skylake-Client-IBRS</model>
      <vendor>Intel</vendor>
...

3. start a guest with host-model cpu and recheck qemu cmd line and xml:

# virsh dumpxml vm1 --update-cpu
...
  <cpu mode='host-model' match='exact'>
    <model fallback='forbid'>Skylake-Client-IBRS</model>
    <vendor>Intel</vendor>

# ps aux|grep qemu
 -cpu Skylake-Client-IBRS,..(no spec-ctrl)...
Comment 9 errata-xmlrpc 2018-01-25 12:59:10 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0188
Note You need to log in before you can comment on or make changes to this bug.