aboutsummaryrefslogtreecommitdiff
path: root/linux-user/nios2/cpu_loop.c
diff options
context:
space:
mode:
authorDaniel Henrique Barboza <danielhb413@gmail.com>2021-12-17 17:57:13 +0100
committerCédric Le Goater <clg@kaod.org>2021-12-17 17:57:13 +0100
commitebe6c3fab8614a26130f7c72dd35ecede11a0f71 (patch)
tree2771954c79a65a07b1f71fc81996855c45f8cef7 /linux-user/nios2/cpu_loop.c
parent58c49ef5c4c367d13c51e7d488611f884fdd6ac8 (diff)
downloadqemu-ebe6c3fab8614a26130f7c72dd35ecede11a0f71.zip
qemu-ebe6c3fab8614a26130f7c72dd35ecede11a0f71.tar.gz
qemu-ebe6c3fab8614a26130f7c72dd35ecede11a0f71.tar.bz2
ppc/pnv.c: add a friendly warning when accel=kvm is used
If one tries to use -machine powernv9,accel=kvm in a Power9 host, a cryptic error will be shown: qemu-system-ppc64: Register sync failed... If you're using kvm-hv.ko, only "-cpu host" is possible qemu-system-ppc64: kvm_init_vcpu: kvm_arch_init_vcpu failed (0): Invalid argument Appending '-cpu host' will throw another error: qemu-system-ppc64: invalid chip model 'host' for powernv9 machine The root cause is that in IBM PowerPC we have different specs for the bare-metal and the guests. The bare-metal follows OPAL, the guests follow PAPR. The kernel KVM modules presented in the ppc kernels implements PAPR. This means that we can't use KVM accel when using the powernv machine, which is the emulation of the bare-metal host. All that said, let's give a more informative error in this case. Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com> Reviewed-by: David Gibson <david@gibson.dropbear.id.au> Message-Id: <20211130133153.444601-2-danielhb413@gmail.com> Signed-off-by: Cédric Le Goater <clg@kaod.org>
Diffstat (limited to 'linux-user/nios2/cpu_loop.c')
0 files changed, 0 insertions, 0 deletions