Re: [libvirt] [Qemu-devel] Modern CPU models cannot be used with libvirt

>> We would continue to have Westmere/etc in QEMU exposed as part of the >> user configuration. But I don't think it makes a lot of sense to have >> to modify QEMU any time a new CPU comes out. > > We have to. New features often come with new MSRs which need to be live > migrated, and of course the cpu flags as well. We may push all these to > qemu data files, but this is still qemu. We can't let a management tool > decide that cpu feature X is safe to use on qemu version Y. I think QEMU should own CPU definitions.

I think a management tool should have the choice of whether they are used though because they are a policy IMHO. It's okay for QEMU to implement some degree of policy as long as a management tool can override it with a different policy.