Bug 1508010 - Post libvirt upgrade to 3.2.0-14, migration fails with -- "can't apply global Haswell-noTSX-x86_64-cpu.cmt=off: Property '.cmt' not found" [RHEL 7.4.z]
Summary: Post libvirt upgrade to 3.2.0-14, migration fails with -- "can't apply global...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.4
Hardware: x86_64
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Libvirt Maintainers
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-31 16:52 UTC by Paul Needle
Modified: 2021-06-10 13:24 UTC (History)
24 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1495171
Environment:
Last Closed: 2017-11-01 11:46:48 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Paul Needle 2017-10-31 16:52:51 UTC 
+++ This bug was initially created as a clone of Bug #1495171 +++

Description of problem:

Customer is applying the latest updates on their RHOSP8 overcloud. However, as they need to live-migrate the instances between the upgraded compute nodes (as the node has to be rebooted to apply the updates) to avoid guest downtime, migration fails with libvirt errors mentioning a disabled CPU property that is not found by the hypervisor:

~~~
2017-09-22 16:29:52.457 50466 ERROR nova.virt.libvirt.driver [req-d8675da4-9c0d-4993-9850-beae5159f008 5ebbe90c089647d9a5a9ad55cb67fed5 1058aeb310b944929945a7b177fd66f3 - - -] [instance: 92a68a77-6e75-43e5-9e7f-1392838ef18f] Live Migration failure: internal error: qemu unexpectedly closed the monitor: 2017-09-22T15:29:52.179516Z qemu-kvm: -chardev pty,id=charserial1: char device redirected to /dev/pts/5 (label charserial1)
2017-09-22T15:29:52.198139Z qemu-kvm: can't apply global Haswell-noTSX-x86_64-cpu.cmt=off: Property '.cmt' not found
2017-09-22 16:29:52.577 50466 ERROR nova.virt.libvirt.driver [req-d8675da4-9c0d-4993-9850-beae5159f008 5ebbe90c089647d9a5a9ad55cb67fed5 1058aeb310b944929945a7b177fd66f3 - - -] [instance: 92a68a77-6e75-43e5-9e7f-1392838ef18f] Migration operation has aborted
~~~


Version-Release number of selected component (if applicable):

Same on both source and target nodes

libvirt-3.2.0-14.el7_4.3.x86_64 
openstack-nova-api-12.0.6-17.el7ost.noarch
openstack-nova-cert-12.0.6-17.el7ost.noarch
openstack-nova-common-12.0.6-17.el7ost.noarch
openstack-nova-compute-12.0.6-17.el7ost.noarch
openstack-nova-conductor-12.0.6-17.el7ost.noarch
openstack-nova-console-12.0.6-17.el7ost.noarch
openstack-nova-migration-12.0.6-17.el7ost.noarch
openstack-nova-novncproxy-12.0.6-17.el7ost.noarch
openstack-nova-scheduler-12.0.6-17.el7ost.noarch
python-nova-12.0.6-17.el7ost.noarch
python-novaclient-3.1.0-2.el7ost.noarch


Expected results:

Live migration works fine to reduce instances downtime
Note You need to log in before you can comment on or make changes to this bug.