I would be curious if specifing the cpu type would actually restrict performance. As far as I know, this only restricts the cpu features presented to a vm. You can present a vm that has the cpu instruction sets of a Pentium 3 – but runs and is as performant as a single core on a 2.8ghz hexcore cpu. Additionally one would have to change that for the entire HV. You might have better luck also using the flavor extra_specs: http://docs.openstack.org/admin-guide-cloud/compute-flavors.html I am pretty sure thought you can't set what CPU type/flags to present to the vm through them though. (Maybe with custom code) ___________________________________________________________________ Kris Lindgren Senior Linux Systems Engineer GoDaddy From: Mike Smith <mismith at overstock.com<mailto:mismith at overstock.com>> Date: Thursday, March 3, 2016 at 2:06 PM To: Jonathan Proulx <jon at csail.mit.edu<mailto:jon at csail.mit.edu>> Cc: "openstack-operators at lists.openstack.org<mailto:openstack-operators at lists.openstack.org>" <openstack-operators at lists.openstack.org<mailto:openstack-operators at lists.openstack.org>> Subject: Re: [Openstack-operators] libvirt cpu type per instance? Jonathan - There are some nova settings (at least for KVM that you are probably thinking of, such as: cpu_mode cpu_model http://docs.openstack.org/liberty/config-reference/content/kvm.html Mike Smith Lead Cloud Systems Architect Overstock.com<http://Overstock.com> On Mar 3, 2016, at 1:52 PM, Jonathan Proulx <jon at csail.mit.edu<mailto:jon at csail.mit.edu>> wrote: I have a user who wants to specify their libvirt CPU type to restrict performance because they're modeling embeded systems. I seem to vaguely recall there is/was a way to specify this either in the instance type or maybe even in the image metadata, but I can't seem to find it. Am I delusional or blind? -Jon -- _______________________________________________ OpenStack-operators mailing list OpenStack-operators at lists.openstack.org<mailto:OpenStack-operators at lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160303/b743ae2c/attachment.html>