On Fri, Mar 16, 2018 at 05:44:28PM +0000, Daniel P. Berrangé wrote: > Since Xen lets you specify raw "cpuid" register values here, surely > this is flexible enough to allow us to support the mode=custom CPU > models ? > > We would just need to make sure every bit poisition used either > 0 or 1, and not 'x', so that we are fully overriding whatever > defaults are presented by the hypervisor "host" CPU model. Or is > life more complicated than that ? This is what v1 of this series had... See discussion there, especially message from Jiri: https://www.redhat.com/archives/libvir-list/2017-June/msg01304.html And this, from... you: https://www.redhat.com/archives/libvir-list/2017-June/msg01308.html This is not only about 'x'. But also about setting '1' where hardware does not really support given feature. This will also result in "broken" CPU. -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?
Attachment:
signature.asc
Description: PGP signature
-- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
