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 optional return values to query-cpu-definitions, stating for
each returned CPU definition, if it is migration-safe and if it is static.
Signed-off-by: David Hildenbrand <d...@linux.vnet.ibm.com>
---
qapi-schema.json | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/qapi-schema.json b/qapi-schema.json
index 5658723..3f50c1d 100644
--- a/qapi-schema.json
+++ b/qapi-schema.json
@@ -3038,10 +3038,19 @@
#
# @name: the name of the CPU definition
#
+# @migration-safe: #optional whether a CPU definition can be safely used for
+# migration in combination with a QEMU compatibility machine
+# when migrating between different QMU versions and hosts.
+# If not provided, information is not available.
+#
+# @static: #optional whether a CPU definition is static and will not change
+# between QEMU versions / QEMU machines. A static model is always
+# migration-safe. If not provided, information is not available.
+#
# Since: 1.2.0
##
{ 'struct': 'CpuDefinitionInfo',
- 'data': { 'name': 'str' } }
+ 'data': { 'name': 'str', '*migration-safe' : 'bool', '*static' : 'bool' } }
##
# @query-cpu-definitions:
--
2.6.6
