Am 23.06.2015 um 19:45 schrieb Eduardo Habkost: > On Tue, Jun 23, 2015 at 07:41:50PM +0200, Andreas Färber wrote: > [...] >> If that is the whole problem here, then why not just add a global flag >> to only enable explicitly requested KVM features? All other features >> should not depend on the host, and the whole discussion about -x.y seems >> like a distraction. > > Now replace "KVM features" with "CPU fatures", because all CPU features > are KVM features, as all of them depend on KVM code enabling them on > GET_SUPPORTED_CPUID. > > Thus, the global flag to only enable explicitly request KVM features on > CPUs is "-cpu custom", which doesn't enable any CPU feature at all.
If libvirt wants to use an empty CPU model, then why export our models to libvirt? I don't mind there being an optional custom model, I mind our compat_props getting ignored that way, which are unrelated to adding new features, in fact they suppress just that for the -2.3 examples. Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton; HRB 21284 (AG Nürnberg)
