Reasons a Windows VM Restarted Unexpectedly
How to diagnose why a Windows VM restarted unexpectedly by reviewing VergeOS log messages including kill, poweroff, shutdown, and reset events.
If you have a Windows VM that has recently restarted unexpectedly, the first place to begin is to review the logs from the VM dashboard. You can reach the log viewer by navigating from the Main Menu > Machines > Virtual Machines > the name of the VM you are investigating > Logs.
From the Log view, search through (or filter the results) under the Message section. Several status messages will indicate why the VM stopped running. The following are the most common and a brief explanation of each:
Message: VM action 'kill' sent This indicates that a VergeOS user issued a Kill Power command from the VergeOS interface. The log will indicate the user under the Source column. In this scenario, consult with the system user to determine the reason for issuing this command.
Message: VM action 'poweroff' sent This indicates that a VergeOS user issued a graceful Power Off command from the VergeOS interface. This command successfully interacted with the Guest OS ACPI to gracefully stop the VM. The log will indicate the user under the Source column. In this scenario, consult with the system user to determine the reason for issuing this command.
Message: VM has shutdown This indicates that the shutdown command was issued from inside the guest operating system directly. In this scenario, consult with the guest operating system logs to determine the reason for the shutdown command.
Message: VM has reset This indicates that the restart command was issued from inside the guest operating system directly. In this scenario, consult with the guest operating system logs to determine the reason for the reset command.
Last updated
Was this helpful?