diff options
| author | Greg Kurz <groug@kaod.org> | 2018-05-03 23:16:48 +0200 |
|---|---|---|
| committer | David Gibson <david@gibson.dropbear.id.au> | 2018-05-04 15:00:37 +1000 |
| commit | aef19c04bf88e0f5f936301e6c29b239e488fbc6 (patch) | |
| tree | be215373fde2ce12cfedadabe283c4bbb2c70d87 /qapi | |
| parent | bce009645b9f1d59195518e35747c8ea30f985f7 (diff) | |
| download | qemu-aef19c04bf88e0f5f936301e6c29b239e488fbc6.zip qemu-aef19c04bf88e0f5f936301e6c29b239e488fbc6.tar.gz qemu-aef19c04bf88e0f5f936301e6c29b239e488fbc6.tar.bz2 | |
spapr: don't migrate "spapr_option_vector_ov5_cas" to pre 2.8 machines
a324d6f16697 "spapr: Support ibm,dynamic-memory-v2 property" added
a new feature in the set of CAS-negotiatable options. This causes
the CAS-negotiated options subsection to be migrated, even for old
machine types that don't know about it, and breaks backward migration
to QEMU 2.7 and older versions:
qemu-system-ppc64: error while loading state for instance 0x0 of device
'spapr'
qemu-system-ppc64: load of migration failed: No such file or directory
Since this feature only affects boot time behaviour, it should be
filtered out when we decide to migrate CAS-negotiated options, like
we already do with OV5_FORM1_AFFINITY and OV5_DRCONF_MEMORY.
Signed-off-by: Greg Kurz <groug@kaod.org>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Diffstat (limited to 'qapi')
0 files changed, 0 insertions, 0 deletions