qemu/target/s390x/kvm
Thomas Huth 7af51621b1 target/s390x/kvm/pv: Provide some more useful information if decryption fails
It's a common scenario to copy guest images from one host to another
to run the guest on the other machine. This (of course) does not work
with "secure execution" guests since they are encrypted with one certain
host key. However, if you still (accidentally) do it, you only get a
very user-unfriendly error message that looks like this:

 qemu-system-s390x: KVM PV command 2 (KVM_PV_SET_SEC_PARMS) failed:
  header rc 108 rrc 5 IOCTL rc: -22

Let's provide at least a somewhat nicer hint to the users so that they
are able to figure out what might have gone wrong.

Buglink: https://issues.redhat.com/browse/RHEL-18212
Message-ID: <20240110142916.850605-1-thuth@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Reviewed-by: Cédric Le Goater <clg@redhat.com>
Reviewed-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
2024-01-11 14:12:59 +01:00
..
kvm_s390x.h s390x/cpu topology: resetting the Topology-Change-Report 2023-10-20 07:16:53 +02:00
kvm.c system/cpus: rename qemu_mutex_lock_iothread() to bql_lock() 2024-01-08 10:45:43 -05:00
meson.build target/s390x/cpu topology: handle STSI(15) and build the SYSIB 2023-10-20 07:16:53 +02:00
pv.c target/s390x/kvm/pv: Provide some more useful information if decryption fails 2024-01-11 14:12:59 +01:00
pv.h target/s390x/kvm/pv: Provide some more useful information if decryption fails 2024-01-11 14:12:59 +01:00
stsi-topology.c target/s390x/cpu topology: Fix ordering and creation of TLEs 2023-11-07 19:27:08 +01:00
stubs.c s390x: Add protected dump cap 2022-10-26 12:54:30 +04:00
trace-events trace-events: Fix the name of the tracing.rst file 2023-09-08 13:08:51 +03:00
trace.h target/s390x: move kvm files into kvm/ 2021-07-07 14:01:59 +02:00