vrunner: warn on shutdown-escalation that state disk may be corrupted

When the guest doesn't exit within the daemon_stop() poll window, the
graceful_shutdown() didn't complete and the state disk's ext4 journal
may have unflushed writes from this session. Any subsequent escalation
(QMP quit, SIGTERM, SIGKILL) leaves the disk image at risk of corruption:
layer files end up with correct inode metadata but partially-unwritten
data extents, surfacing on the next session as

  Error: reading blob sha256:<hash>: EOF
  Error: reading blob sha256:<hash>: file integrity checksum failed
         for "<file>"

These errors are silent today — the operator hits them later in another
session with no way to correlate back to the original cause. Emit a
WARN as soon as the poll window expires, naming the symptom and pointing
at the remediation (`memres restart --clean`) so the next session starts
from a known-good state instead of inheriting a corrupted image.

This is purely diagnostic — no behavior change to the shutdown sequence
itself. The escalation paths (QMP quit, SIGTERM, SIGKILL) still run
unchanged.

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>

0 files changed, 0 insertions, 0 deletions