On 10/27/2016 11:09 PM, William Josefsson wrote:
hi, I did 'virsh capabilities' on the Haswell, which turned out to
list model: Haswell-noTSX. So I set in nova.conf
cpu_model=Haswell-noTSX on both Haswell and Broadwell hosts and it
seems to work. I believe this is my smallest common denominator.
hi, I did 'virsh capabilities' on the Haswell, which turned out to
list model: Haswell-noTSX. So I set in nova.conf
cpu_model=Haswell-noTSX on both Haswell and Broadwell hosts and it
seems to work. I believe this is my smallest common denominator. thx
will
On Fri, Oct 28, 2016 at 2:39 AM,
Depending on your workload, it will. If they depend on any custom CPU
extensions, they will miss out on them and performance will be
decreased. My personal suggestion is to read the docs for it and use
the "smallest common denominator" in terms of CPU usage.
On Thu, Oct 27, 2016 at 11:31 AM,
On Thu, Oct 27, 2016 at 5:20 PM, Chris Friesen
wrote:
> In your case you probably want to set both computes to have:
>
> [libvirt]
> cpu_mode = custom
> cpu_model = Haswell
>
Hi Chris, thanks! Yerps, I finally got it working. However, I set
cpu_model=kvm64
On 10/26/2016 06:07 AM, William Josefsson wrote:
Hi list,
I'm facing issues on Liberty/CentOS7 doing live migrations between to
hosts. The hosts are Haswell and Broadwell. However, there is not
feature specific running on my VMs
Haswell -> Broadwell works
Broadwell -> Haswell fails with the
Thank you Mohammed. So I just set cpu_mode=none in libvirt section on
both source and destination hosts, restart nova-compute, restart VMs
on source host, and finally do the live migration? pls let me know if
this is wrong. thx will
On Wed, Oct 26, 2016 at 11:45 PM, Mohammed Naser
The VMs have to be restarted so that the libvirt config is updated
with the new CPU model.
Good luck!
On Wed, Oct 26, 2016 at 8:07 AM, William Josefsson
wrote:
> Hi list,
>
> I'm facing issues on Liberty/CentOS7 doing live migrations between to
> hosts. The hosts are