# Revision history [back]

After discussions on the #openstack-nova channel, it IS a libvirt bug / regression due on the newly backported package.

As it seems to be corrected in the upstream libvirt with commit de0aeafe9ce3eb414c8b5d3aa8995d776a2952de, does anybody know how to contact the maintainers of the http://archive.gplhost.com/debian icehouse-backports repository in order to ask them to backport the libvirt-bin package ?

Thanx again !

After discussions on the #openstack-nova channel, it IS a libvirt bug / regression due on the newly backported package.

As it seems to be corrected in the upstream libvirt with commit de0aeafe9ce3eb414c8b5d3aa8995d776a2952de, does anybody know how to contact the maintainers of the http://archive.gplhost.com/debian archive.gplhost.com/debian icehouse-backports repository in order to ask them to backport the libvirt-bin package ?

Thanx again !

After discussions on the #openstack-nova channel, it IS a libvirt bug / regression due on the newly backported package.

As it seems to be corrected in the upstream libvirt with commit de0aeafe9ce3eb414c8b5d3aa8995d776a2952de, does anybody know how to contact the maintainers of the archive.gplhost.com/debian icehouse-backports repository in order to ask them to backport the libvirt-bin package ?

Thanx again !

Update :

ugly but working workaround :

comment the invtsc feature in /usr/share/libvirt/cpu_map.xml

 <!-- Advanced Power Management edx features -->
<!--
<feature name='invtsc'>
<cpuid function='0x80000007' edx='0x00000100'/>
</feature>
-->


Restart libvirt service

Restart nova-compute service

Et voilà...