diff options
| author | Cornelia Huck <cohuck@redhat.com> | 2025-09-11 17:41:59 +0200 |
|---|---|---|
| committer | Peter Maydell <peter.maydell@linaro.org> | 2025-09-16 17:31:54 +0100 |
| commit | 19f6dcfe6b8b2a3523362812fc696ab83050d316 (patch) | |
| tree | 7f68204cda879a7ef023d339d229d9db0cee8f23 /scripts/lib/kdoc/kdoc_parser.py | |
| parent | 116c2c21d521eb31fffb44eb74d918975c9a5658 (diff) | |
| download | qemu-19f6dcfe6b8b2a3523362812fc696ab83050d316.zip qemu-19f6dcfe6b8b2a3523362812fc696ab83050d316.tar.gz qemu-19f6dcfe6b8b2a3523362812fc696ab83050d316.tar.bz2 | |
arm/kvm: report registers we failed to set
If we fail migration because of a mismatch of some registers between
source and destination, the error message is not very informative:
qemu-system-aarch64: error while loading state for instance 0x0 ofdevice 'cpu'
qemu-system-aarch64: Failed to put registers after init: Invalid argument
At least try to give the user a hint which registers had a problem,
even if they cannot really do anything about it right now.
Sample output:
Could not set register op0:3 op1:0 crn:0 crm:0 op2:0 to c00fac31 (is 413fd0c1)
We could be even more helpful once we support writable ID registers,
at which point the user might actually be able to configure something
that is migratable.
Suggested-by: Eric Auger <eric.auger@redhat.com>
Reviewed-by: Sebastian Ott <sebott@redhat.com>
Signed-off-by: Cornelia Huck <cohuck@redhat.com>
Message-id: 20250911154159.158046-1-cohuck@redhat.com
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Diffstat (limited to 'scripts/lib/kdoc/kdoc_parser.py')
0 files changed, 0 insertions, 0 deletions