The cpu model actually gets read from a libvirt xml file. Extensive documentation about this can be found here: http://wiki.libvirt.org/page/Libvirt_identifies_host_processor_as_a_different_model_from_the_hardware_documentation
HTH Am 04.04.2014 17:32, schrieb Itamar Heim: > On 03/31/2014 06:57 PM, Robert Story wrote: >> On Wed, 19 Mar 2014 10:13:28 -0400 (EDT) Omer wrote: >> OF> cpu name is cluster level, and usually the lowest common >> denominator of >> OF> the hosts in cluster, to make sure migration works in the cluster. >> >> Is there and documentation on the relationship between cpu types and >> compatibility? Right now I have a cluster per cpu type, and it might make >> sense to merge some of them if the performance hit was minimal. > > that would be a question for qemu-kvm - they provide the cpu models we > base this on. > you can check which cpu flags you get exposed in the guest of the higher > cpu model, then check if you think your applications would care about > them... -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users