On Thu, Dec 15, 2011 at 08:58:55 -0600, Anthony Liguori wrote: > Pass '-readconfig /etc/qemu/target-x86_64.conf' to pick up those models and if > you are absolutely insistent on not giving the user any ability to change things > on their own, cp the file from qemu.git into libvirt.git and install it in a > safe place. Ah, this looks like a good idea (and we could even generate that file dynamically if we add support for family/stepping/... and other things that we do not model now). However, separating these definitions from qemu may result in incompatibilities with older qemu versions. I guess mainly because our configuration file would mention a CPU feature that an installed qemu version doesn't understand. Currently, qemu seems to just ignore such feature (although it prints an error) and continues happily without it. Is there any way for us to ask qemu what CPU features it knows about so that we could avoid using a CPU models which include features qemu doesn't understand? Jirka -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list