[Bug 1551963] Re: wrong haswell cpu features in cpu_map.xml

[ChristianEhrhardt]

Hi,
sorry for coming by this bug so late, the same is true up until latest Libvirt.

Yet the detail is different, there always can still be unpatched systems out there.
So one can't change the type.

In fact it was a new type introduced which is "..-noTSX".
Think of it as a second HW-revision.

The CPU should be correctly detected to be that newer type.
http://libvirt.org/git/?p=libvirt.git;a=commitdiff;h=c563b50605ae9895b981d198e11dbe9f6e18027b
This fix is in Xenial and later (maybe even in Wily).

Officially that got into: v1.2.14

One needs to check and maybe backport the kilo/cloud version.

Look for <model name='Haswell-noTSX'>, subscribing the cloud Team

** Also affects: cloud-archive
   Importance: Undecided
       Status: New

** Changed in: libvirt (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
https://bugs.launchpad.net/bugs/1551963

Title:
  wrong haswell cpu features in cpu_map.xml

Status in Ubuntu Cloud Archive:
  New
Status in libvirt package in Ubuntu:
  Fix Released

Bug description:
  for haswell, /usr/share/libvirt/cpu_map.xml lists the following:

      <model name='Haswell'>
        <model name='SandyBridge'/>
        <feature name='fma'/>
        <feature name='pcid'/>
        <feature name='movbe'/>
        <feature name='fsgsbase'/>
        <feature name='bmi1'/>
        <feature name='hle'/>
        <feature name='avx2'/>
        <feature name='smep'/>
        <feature name='bmi2'/>
        <feature name='erms'/>
        <feature name='invpcid'/>
        <feature name='rtm'/>
      </model>

  "hle" and "rtm" has been pulled from haswell via microcode updates
  which means that with the current map, libvirt will never identify
  Haswell CPUs properly.

  This will prevent OpenStack deployments from properly setting up their
  VMs which will prevent live-migration.

  Just for the record, these are the ones available on a E5-2630v3:
  fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid cqm xsaveopt cqm_llc cqm_occup_llc

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1551963/+subscriptions