| Previous | Next |
| ERROR_VMCOMPUTE_INVALID_STATE | ERROR_VMCOMPUTE_TERMINATED |
ERROR_VMCOMPUTE_UNEXPECTED_EXIT
An unexpected exit is a runtime failure, not merely a failed API call
ERROR_VMCOMPUTE_UNEXPECTED_EXIT applies after a compute system had progressed beyond initial startup and then stopped unexpectedly. The cause can be inside the guest or container workload, in the utility VM, or in the host virtualization and storage path.
Because HCS systems are cleaned up after stopping, postmortem data must be captured promptly. The exit event, compute-system properties, result JSON, guest process exit information and matching host event-log entries are more useful than repeatedly creating a replacement that fails in the same way.
Evidence and corrective action
- Capture the HCS exit event and query any remaining exit-status properties before closing the final handle.
- For a container, distinguish termination of the configured initial process from a failure of the hosting utility VM.
- Correlate the compute-system ID with Host Compute Service, Hyper-V Compute and storage-layer events.
- Preserve crash dumps or container logs outside the ephemeral writable layer when possible.
- Compare the failure with resource pressure, host servicing and image changes at the same timestamp.
References
- Microsoft: Host Compute System overview
- Microsoft: HCS event callbacks
- Microsoft: HcsGetComputeSystemProperties
Looking for a different code? Search another status or error code.