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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1551963 Title: wrong haswell cpu features in cpu_map.xml To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1551963/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
