Nova live migration fails - InvalidCPUInfo: Unacceptable CPU info: CPU doesn't have compatibility.
Chris Friesen
chris.friesen at windriver.com
Fri Dec 14 16:26:09 UTC 2018
On 12/14/2018 9:38 AM, Torin Woltjer wrote:
> I've restarted the instances that I'm using to test but no luck.
>
> I have the setting set on just the highest compute node; I tried setting
> it on one of my older gen compute nodes as well but because there is
> production load on it, I am anxious about restarting services; I did
> restart the nova-compute service after making the change and there was
> no change in behavior. Should the setting also be set on the controllers?
You should set the model explicitly on all the nodes, you'd only need to
restart nova-compute on that node after changing the setting.
It might be worth booting up an instance on the G4 node after making
this change and then checking whether the XML matches what you have on
the G5 node.
Chris
More information about the openstack-discuss
mailing list