On 08/29/2016 05:13 AM, David Hildenbrand wrote: > It might be of interest for tooling whether a CPU definition can be safely > used when migrating, or if e.g. CPU features might get lost during > migration when migrationg from/to a different QEMU version or host, even if > the same compatibility machine is used. > > Also, we want to know if a CPU definition is static and will never change. > Beause these definitions can then be used independantly of a compatibility > machine and will always have the same feature set, they can e.g. be used > to indicate the "host" model in libvirt later on. > > Let's add two return values to query-cpu-definitions, stating for each > returned CPU definition, if it is migration-safe and if it is static. > > While "migration-safe" is optional, "static" will be set to "false" > automatically by all implementing architectures. If a model really was > static all the time and will be in the future, this can simply be changed > later. > > Signed-off-by: David Hildenbrand <d...@linux.vnet.ibm.com> > --- > qapi-schema.json | 14 +++++++++++++- > 1 file changed, 13 insertions(+), 1 deletion(-)
Reviewed-by: Eric Blake <ebl...@redhat.com> -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
