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, Mohammed Naser <[email protected]> wrote: > 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, William Josefsson > <[email protected]> wrote: >> On Thu, Oct 27, 2016 at 5:20 PM, Chris Friesen >> <[email protected]> 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 everywhere and it seems to work. It is listed here: >> https://wiki.openstack.org/wiki/LibvirtXMLCPUModel hopefully 'kvm64' >> has no performance impact what cpu_model is set to, or would 'kvm64' >> as model negatively affect my VMs? thx will >> >> _______________________________________________ >> OpenStack-operators mailing list >> [email protected] >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > > > -- > Mohammed Naser — vexxhost > ----------------------------------------------------- > D. 514-316-8872 > D. 800-910-1726 ext. 200 > E. [email protected] > W. http://vexxhost.com _______________________________________________ OpenStack-operators mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
