diff options
author | Laurent Vivier <lvivier@redhat.com> | 2017-12-14 19:09:48 +0100 |
---|---|---|
committer | David Gibson <david@gibson.dropbear.id.au> | 2017-12-15 09:50:29 +1100 |
commit | 1481fe5fcfeb7fcf3c1ebb9d8c0432e3e0188ccf (patch) | |
tree | 1f8b37d891ec6ec4c7fccd6f7950b654def16517 /po/it.po | |
parent | 4f441474c61f317de7927edfdb1d042b0b6f3882 (diff) | |
download | qemu-1481fe5fcfeb7fcf3c1ebb9d8c0432e3e0188ccf.zip qemu-1481fe5fcfeb7fcf3c1ebb9d8c0432e3e0188ccf.tar.gz qemu-1481fe5fcfeb7fcf3c1ebb9d8c0432e3e0188ccf.tar.bz2 |
spapr: don't initialize PATB entry if max-cpu-compat < power9
if KVM is enabled and KVM capabilities MMU radix is available,
the partition table entry (patb_entry) for the radix mode is
initialized by default in ppc_spapr_reset().
It's a problem if we want to migrate the guest to a POWER8 host
while the kernel is not started to set the value to the one
expected for a POWER8 CPU.
The "-machine max-cpu-compat=power8" should allow to migrate
a POWER9 KVM host to a POWER8 KVM host, but because patb_entry
is set, the destination QEMU tries to enable radix mode on the
POWER8 host. This fails and cancels the migration:
Process table config unsupported by the host
error while loading state for instance 0x0 of device 'spapr'
load of migration failed: Invalid argument
This patch doesn't set the PATB entry if the user provides
a CPU compatibility mode that doesn't support radix mode.
Signed-off-by: Laurent Vivier <lvivier@redhat.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Diffstat (limited to 'po/it.po')
0 files changed, 0 insertions, 0 deletions