On Fri, Jun 29, 2018 at 08:06:04AM +0200, Jiri Denemark wrote: > On Thu, Jun 28, 2018 at 16:23:53 -0300, Eduardo Habkost wrote: > > On Thu, Jun 28, 2018 at 07:59:38PM +0100, Dr. David Alan Gilbert wrote: [...] > > > Would you restrict the combinations to cut down the test matrix - e.g. > > > not allow Haswell-3.0.0 on anything prior to a 2.12 machine type? > > > > Not sure if it would be worth the extra complexity: we would need > > an interface to tell libvirt which CPU models are usable on which > > machine-types. > > In case we do this, libvirt should already by ready for it on the API > level for both reporting capabilities and CPU comparison/baseline. All > these APIs already accept machine type as an optional parameter so that > different results can be provided depending on machine type. Does it have an abstraction that can already represent "CPU model $C can/can't be used with machine-type $M"? -- Eduardo -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
