> I'm encountering an issue with live migrating between 2 Compute nodes with
> different CPU models. Host A has a Westmere CPU and host B has a Broadwell.
That’s expected unless you specify the least common denominator with the cpu
model, in this case Westmere, when you boot the instances.
>
Dear all,
A gentle reminder for our meeting tomorrow.
As usual, the agenda is available at:
https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2017 (line
860)
Please feel free to add items.
Best,
Adrien
PS: note that due to the vacation period, I don't know how many persons wi
Hi, I have a doubt regarding the upgrade of openstack, it is possible to
upgrade from an old version or an updated one without going through the
intermediate versions.
Example: kilo to newton
Or it must be incremental kilo, liberty, mitaka, newton.
In my experience I always did them incremental
Hi,
Thanks for the suggestion, but it’s still not working. I have changed both
nodes to use the Westmere CPU model, which is the lowest common CPU instruction
set. The following is in the nova.conf on both nodes;
cpu_mode = custom
cpu_model = Westmere
libvirt_cpu_mode = custom
libvirt_cpu_model
Hello..
can you send cpu info(/proc/cpuinfo or dmidecode)?
see =>
https://wiki.libvirt.org/page/Libvirt_identifies_host_processor_as_a_different_model_from_the_hardware_documentation
https://serverfault.com/questions/585791/which-cpu-model-to-set-for-guest-kvm-when-processor-is-ivy-bridge
lib
Thanks for the advice and feedback!
>> I'm encountering an issue with live migrating between 2 Compute nodes with
>> different CPU models. Host A has a Westmere CPU and host B has a Broadwell.
>That’s expected unless you specify the least common denominator with the cpu
>model, in this case Wes
>Hello..
>can you send cpu info(/proc/cpuinfo or dmidecode)?
Westmere host /proc/cpuinfo:
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 44
model name : Intel(R) Xeon(R) CPU E5640 @ 2.67GHz
stepping: 2
microcode : 0x1d
cpu M
