It's worth cleaning up all resources that the guest taking and to quit if an exception in el1 could not be resolved.
Otherwise, the guest will get in the infinite black-hole by unmodified pc. Signed-off-by: Leesoo Ahn <[email protected]> --- target/arm/hvf/hvf.c | 1 + 1 file changed, 1 insertion(+) diff --git a/target/arm/hvf/hvf.c b/target/arm/hvf/hvf.c index 8b902c6882..4358cf90e8 100644 --- a/target/arm/hvf/hvf.c +++ b/target/arm/hvf/hvf.c @@ -2533,6 +2533,7 @@ static int hvf_handle_exception(CPUState *cpu, hv_vcpu_exit_exception_t *excp) cpu_synchronize_state(cpu); trace_hvf_exit(syndrome, ec, env->pc); error_report("0x%llx: unhandled exception ec=0x%x", env->pc, ec); + qemu_system_guest_panicked(cpu_get_crash_info(cpu)); } /* flush any changed cpu state back to HVF */ --- base-commit: b83371668192a705b878e909c5ae9c1233cbd5fb change-id: 20260623-guest-panic-unhandle-4921d2aa69fb Best regards, -- Leesoo Ahn <[email protected]>
