# DF-3037 run.2.log -- post-trigger guest-liveness probes (baseline kernel #0)
#
# After run.log's step [5] (cycle rename hung, kill -9 ineffective), the
# capture ssh session itself stalled mid-script and was killed by a 180 s
# host-side timeout. These follow-up probes were then run from the host:
#
#   $ timeout 30 ssh -F dfbsd-qemu/config dfbsd-maxx 'date; uptime'
#   Connection timed out during banner exchange
#   probe_rc=255
#
#   $ dfbsd-qemu/vm.sh status
#   down            (status probe = ssh 'true' fails)
#
#   $ tail -5 dfbsd-qemu/boot.log      (QEMU serial console)
#   DragonFly/x86_64 (dfbsd) (ttyd0)
#   login: vn0: MBR magic not found; assume a COMPATIBILITY_SLICE (s0)
#   vn0: MBR magic not found; assume a COMPATIBILITY_SLICE (s0)
#
# Interpretation: TCP port-forward still answers (QEMU alive) but sshd can no
# longer complete a login (no banner) -> guest userspace is wedged system-wide
# by the single spinning doscheckpath loop; NO panic on serial. This is the
# "ssh dies AND vm.sh status => down right after" row of the status table:
# livelock DoS (serial console shows no crash dump). The exact command outputs
# above are transcribed from the audit session log (stderr of the live probe);
# the guest was subsequently reset for fix validation, so they cannot be
# re-captured on the wedged state.