错误：实例热迁移到主机"compute06"失败 Failed to compute_task_migrate_server: Unacce

admin

2022-06-21 14:47:33.988 25 WARNING oslo_config.cfg [req-b990f037-8329-4f82-aba0-2ad6df0942d8 ef9faa1589a945ec9764b05c1c433b57 6f0124196ea74eb79fbcf370add3ca7e - default default] Option "os_region_name" from group "placement" is deprecated. Use option "region-name" from group "placement".
" m! P- g4 E% o+ ]$ M2022-06-21 14:47:36.470 25 WARNING nova.scheduler.utils [req-b990f037-8329-4f82-aba0-2ad6df0942d8 ef9faa1589a945ec9764b05c1c433b57 6f0124196ea74eb79fbcf370add3ca7e - default default] Failed to compute_task_migrate_server: Unacceptable CPU info: CPU doesn't have compatibility.
, W# P2 b8 k9 j  O+ i% X  ?
  M4 A2 s5 {6 I0

Refer to http://libvirt.org/html/libvirt- ... virCPUCompareResult
* n+ `4 C' |6 n- L+ bTraceback (most recent call last):
6 |8 }5 l1 g$ c6 n
  File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/server.py", line 166, in _process_incoming
    res = self.dispatcher.dispatch(message)

- M9 O0 U2 t$ {5 ^" c/ t$ M  File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 220, in dispatch
6 n& \) M/ \# C4 I- n    return self._do_dispatch(endpoint, method, ctxt, args)

3 C: j9 C- W5 K# ?' B) d  File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 190, in _do_dispatch
4 @; m/ v* N# W% e, |. S- g4 w    result = func(ctxt, **new_args)

  File "/usr/lib/python2.7/site-packages/nova/exception_wrapper.py", line 76, in wrapped
    function_name, call_dict, binary)

8 x$ _) f- G. u& ^) }/ `  File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__
# A* [$ d3 p8 u- P8 m- [    self.force_reraise()

- ^4 e: t9 V6 H/ H/ r8 X8 s  File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise
: X1 _' d: V* b* j8 m    six.reraise(self.type_, self.value, self.tb)

5 T4 [/ R& s3 n0 K: ~  File "/usr/lib/python2.7/site-packages/nova/exception_wrapper.py", line 67, in wrapped
/ n4 y) a* T! |/ d& s3 G    return f(self, context, *args, **kw)
9 G1 \6 n3 Q% h( X( T/ ]
. t) z, J$ [- q. U  File "/usr/lib/python2.7/site-packages/nova/compute/utils.py", line 1000, in decorated_function
    return function(self, context, *args, **kwargs)

  File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 215, in decorated_function
+ K, E( ]4 C4 y$ ?# \0 ]    kwargs['instance'], e, sys.exc_info())

7 u8 P: @7 V- v. X: E3 }3 l  File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__
    self.force_reraise()
# F9 K- N$ n5 I! f' o
  File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise
- k, C6 d3 G3 Q    six.reraise(self.type_, self.value, self.tb)

  File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 203, in decorated_function
    return function(self, context, *args, **kwargs)

- B" z& i9 {, f3 q, Z, h  File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 5971, in check_can_live_migrate_destination
$ I# B0 E  T- E  |7 B8 R5 B1 L  j    disk_over_commit)

  File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 5982, in _do_check_can_live_migrate_destination
    block_migration, disk_over_commit)
2 q  D) w+ V2 D  C
  File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 6570, in check_can_live_migrate_destination
5 P& @5 k; @; g3 L' h. K$ u    self._compare_cpu(None, source_cpu_info, instance)
, _! ^( t7 l( [9 l2 ]9 Z
0 W: G5 x  ]- G8 X+ H1 n  File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 6841, in _compare_cpu
# W8 ^' P" G; b, |# k8 Y    raise exception.InvalidCPUInfo(reason=m % {'ret': ret, 'u': u})

! {9 r0 Q1 V- ^7 R0 cInvalidCPUInfo: Unacceptable CPU info: CPU doesn't have compatibility.
2 l, C) g, v3 \. r5 ^; s
0

Refer to http://libvirt.org/html/libvirt- ... virCPUCompareResult
: InvalidCPUInfo_Remote: Unacceptable CPU info: CPU doesn't have compatibility.
2022-06-21 14:47:36.472 25 WARNING nova.scheduler.utils [req-b990f037-8329-4f82-aba0-2ad6df0942d8 ef9faa1589a945ec9764b05c1c433b57 6f0124196ea74eb79fbcf370add3ca7e - default default] [instance: 4e781528-c494-45fe-8c67-15763fd5650c] Setting instance to ACTIVE state.: InvalidCPUInfo_Remote: Unacceptable CPU info: CPU doesn't have compatibility.

admin

Live migration fails with 'Unacceptable CPU info: CPU doesn't have compatibility' between non-rebooted and rebooted compute nodes after in-place OpenStack Platform major upgrade
9 d/ y6 b: n7 B' m$ l; r( n) i" T8 [& R SOLUTION UNVERIFIED - 已更新 2018年四月23日15:25 - English
环境
, e0 M& {5 o! D# tRed Hat OpenStack Platform after major upgrade.
- s+ ]9 x, G/ e7 lRed Hat Enterprise Linux (RHEL) 7 on overcloud nodes.
microcode_ctl-2.1-22.5.el7_4.x86_64 and linux-firmware-20170606-58.gitc990aae.el7_4.noarch installed as part of the upgrade.
8 C' [8 M- \( h( w* u& {Non-rebooted source compute node is running microcode version 59 and rebooted target is running microcode version 58.
The IBPB CPU model is in use on the source node but not the target node.
0 e) u- c7 l' h# G7 Q& L问题
9 f  T8 x; s: a5 [; W" NAfter an in-place OpenStack Platform major upgrade, live migration fails with the following error when the source node has not been rebooted and the target node has:

2 }$ H5 t- S, c" c4 H( F0 G3 IRaw
Unacceptable CPU info: CPU doesn't have compatibility
/ J8 t2 T8 x( w决议
We recommend working with your respective silicon/hardware vendors in order to upgrade target nodes to version 59 of the CPU microcode or later (whichever is recommended by your silicon/hardware vendors).

After updating, confirm whether virsh capabilities reports that microcode version 59 or later is installed on target node and that the IBPB CPU model is in use. If this is the case, then test live migration on a non-production guest first.

Following this, complete similar microcode updates on all of the other hosts within the OSP environment.

+ v6 Y- m% l0 R9 W  c& B根源
, m4 [, N, L0 I) c0 c! HIf Red Hat distributed microcode_ctl and linux-firmware packages are downgraded to microcode version 58 during a major upgrade, the microcode downgrade will only take effect on each node after a reboot.

The latest microcode_ctl and linux-firmware packages from Red Hat do not include resolutions to CVE-2017-5715 (Spectre variant 2) exploit. Red Hat is no longer providing microcode to address Spectre variant 2, due to instabilities introduced that are causing customer systems to not boot. The latest microcode_ctl and linux-firmware packages are reverting these unstable microprocessor firmware changes to versions that were known to be stable and well tested, released prior to the Spectre/Meltdown embargo lift date on January 3rd 2018. The following article provides more detail in relation to this:
! ~5 w; \+ y$ M( w4 w
- E3 V, R5 [; R: ~5 ]# U+ i  k• What CPU microcode is available via the microcode_ctl package to mitigate CVE-2017-5715 (variant 2)?
6 a! N6 s6 x+ ]8 P- B
In certain scenarios (for example if compute nodes are not rebooted during the major upgrade procedure and then target nodes are later rebooted post upgrade but source nodes are not), source nodes could be running microcode version 59 or later whereas rebooted target nodes could be running microcode version 58.

As such, live migrations would then fail with the Unacceptable CPU info: CPU doesn't have compatibility error, because the target node would lack support for required CPU features.
& Z: G; d- U9 R* Q: K
: b. J; z# M! }# u+ K7 ]) N9 g诊断步骤
/ r, \: f6 G* s# h- @+ ^To check which microcode version is actually running on each node, one option would be to run virsh capabilities and review the microcode version= parameter within the output. For example:
+ L0 J* t4 ^/ L; `' H
0 y& `5 v# y; JRaw
$ z2 X# L: U: S) O& p3 C' t<microcode version='58'/>
Alternatively, /proc/cpuinfo provides the microcode version in hexadecimal format. For example:
+ A) J; y. l3 {4 y* W
Raw
$ grep -is '^microcode' /proc/cpuinfo | head -1
microcode   : 0x3a
We can see that the above example reports microcode version 58 is running:

9 y+ `2 G8 Q. A: D; ]0 YRaw
( r4 l8 E5 B) D3 s' \: l- F$ echo "ibase=16;3A" | bc
58

admin

Live Migration Fails With Error: "Unacceptable CPU Info: CPU Doesn't Have Compatibility.
Problem
: s8 s1 _: g: A% ~$ ^3 vAttempts to perform a live migration of an instance fail with the following error.

" u  N- }! s) i/ v, uUnacceptable CPU info: CPU doesn't have compatibility.
6 W% P; A8 {" T* j5 C4 JCopy
Environment
Platform9 Managed OpenStack - v3.6.0 and Higher
0 \# r9 g* k5 a7 D+ T" l3 w  BCause
This error presents itself when CPU model/architecture differ between the source host and destination host even slightly.

( m! }- S3 y- G2 A! wResolution
Run the following command on the host where the VM currently resides to create an XML with the full CPU description.
# virsh capabilities > virsh-caps-[originHostname]-full.xml
4 N, y" Q3 s, f0 h9 h! g. XCopy
3 ^7 }+ @6 u6 w' a7 DEdit the XML file you've generated deleting everything above "[cpu]" and everything below "[/cpu]".
Move the file to the destination host and run the following command which will tell you if there is a legitimate mismatch and on which side it lies.
# virsh cpu-compare virsh-caps-[originHostname]-full.xml
Copy
To determine the specific features that must be masked out, run the following command.
3 b$ R4 C- x& L: E2 @# virsh cpu-baseline virsh-caps-[originHostname]-full.xml
$ [# ^" u  t1 W  a/ J: h4 L+ \' M  {Copy
Mask out the features that do not appear in the output of the command in Step #4 and attempt to migrate the VM again.
( A2 n8 b1 z$ x) \+ D2 |