[openstack-dev] openstack-dev] [nova] Cannot live migrattion, because error:libvirtError: the CPU is incompatible with host CPU: Host CPU does not provide required features: cmt, mbm_total, mbm_local

[何健乐]

Hi, all
When I did live-miration , I met the following error: result = proxy_call(self._autowrap, f, *args, **kwargs)May 14 10:33:11 nova-compute[981335]: File "/usr/lib/python2.7/site-packages/eventlet/tpool.py", line 144, in proxy_call
May 14 10:33:11 nova-compute[981335]: rv = execute(f, *args, **kwargs)
May 14 10:33:11 nova-compute[981335]: File "/usr/lib/python2.7/site-packages/eventlet/tpool.py", line 125, in execute
May 14 10:33:11 nova-compute[981335]: six.reraise(c, e, tb)
May 14 10:33:11 nova-compute[981335]: File "/usr/lib/python2.7/site-packages/eventlet/tpool.py", line 83, in tworker
May 14 10:33:11 nova-compute[981335]: rv = meth(*args, **kwargs)
May 14 10:33:11 nova-compute[981335]: File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1939, in migrateToURI3
May 14 10:33:11 nova-compute[981335]: if ret == -1: raise libvirtError ('virDomainMigrateToURI3() failed', dom=self)
May 14 10:33:11 nova-compute[981335]: libvirtError: the CPU is incompatible with host CPU: Host CPU does not provide required features: cmt, mbm_total, mbm_local
Is there any one that has solution for this problem.

Thanks

[Chris Friesen]

Post by 何健乐
Hi, all
When I did live-miration , I met the following error: |result
||=||proxy_call(||self||._autowrap, f, ||*||args, ||*||*||kwargs)|
|May ||14| |10||:||33||:||11| |nova||-||compute[||981335||]: ||File|
|"/usr/lib64/python2.7/site-packages/libvirt.py"||, line ||1939||, ||in|
|migrateToURI3|
|May ||14| |10||:||33||:||11| |nova||-||compute[||981335||]: ||if| |ret
||=||=| |-||1||: ||raise| |libvirtError (||'virDomainMigrateToURI3()
failed'||, dom||=||self||)|
|May ||14| |10||:||33||:||11| |nova||-||compute[||981335||]: libvirtError: the
CPU ||is| |incompatible with host CPU: Host CPU does ||not| |provide required
features: cmt, mbm_total, mbm_local|
Is there any one that has solution for this problem.
Thanks

Can you run "virsh capabilities" and provide the "cpu" section for both the
source and dest compute nodes? Can you also provide the "cpu_mode",
"cpu_model", and "cpu_model_extra_flags" options from the "libvirt" section of
/etc/nova/nova.conf on both compute nodes?

Chris

[Sahid Orentino Ferdjaoui]

Post by 何健乐
Hi, all
When I did live-miration , I met the following error: result = proxy_call(self._autowrap, f, *args, **kwargs)May 14 10:33:11 nova-compute[981335]: File "/usr/lib/python2.7/site-packages/eventlet/tpool.py", line 144, in proxy_call
May 14 10:33:11 nova-compute[981335]: rv = execute(f, *args, **kwargs)
May 14 10:33:11 nova-compute[981335]: File "/usr/lib/python2.7/site-packages/eventlet/tpool.py", line 125, in execute
May 14 10:33:11 nova-compute[981335]: six.reraise(c, e, tb)
May 14 10:33:11 nova-compute[981335]: File "/usr/lib/python2.7/site-packages/eventlet/tpool.py", line 83, in tworker
May 14 10:33:11 nova-compute[981335]: rv = meth(*args, **kwargs)
May 14 10:33:11 nova-compute[981335]: File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1939, in migrateToURI3
May 14 10:33:11 nova-compute[981335]: if ret == -1: raise libvirtError ('virDomainMigrateToURI3() failed', dom=self)
May 14 10:33:11 nova-compute[981335]: libvirtError: the CPU is incompatible with host CPU: Host CPU does not provide required features: cmt, mbm_total, mbm_local
Is there any one that has solution for this problem.
Thanks

This could be because you are running an older libvirt version on
destination node which does not know anything about the cache or
memory bandwidth monitoring features from Intel. Upgrading your
libvirt version should resolve the issue.

Or you are effectively trying to live-migrate a host-model domain to a
destination node that does not support such features. To resolve it
you should update your nova.conf to use a CPU model for your guests
that will be compatible for both of your host.

In nova.conf under section libvirt.

cpu_mode=custom
cpu_model=Haswell

Then you should restart nova-compute service and reboot --force the
instance so it will take the new cpu configuration into account.

s.

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-***@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org