Add option to skip cpu feature and model verification in libvirt and rely on qemu 'enforce' option

[Daniel P. Berrangé]

On Wed, Nov 23, 2022 at 11:57:08AM +0000, John Levon wrote:
> On Wed, Nov 23, 2022 at 11:48:17AM +0000, Daniel P. Berrangé wrote:
> 
> > > We're struggling to see what value the libvirt layer is bringing us in this
> > > area, as opposed to a single-source-of-truth approach.
> > 
> > Well libvirt's job is to insulate applications from the specific hypervisor
> > implementation details.
> 
> Sure, of course, this isn't relevant to other drivers or something that would be
> turned on from (say) a virt-manager context. We're not trying to argue this
> should be a default or anything, but this would hardly be the first thing that's
> only supported by the qemu driver.

There's a big difference between a feature only supported by one of
the hypervisor drivers, and a feature where we just blindly do
passthrough of the hypervisor terminology as-is.

With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|