Sometimes, it can be challenging to understand how a Skytap VM ended up in a powered off or suspended state.
Below are some steps that you can take to identify the cause:
- Review Skytap activity tab from within the environment in question
- You may need to review the full auditing log of the environment, which can be accessed from the bottom of the activity tab
- Look to see if automatic power options are enabled in the environment
- View the Skytap Health Dashboard to see if there are any ongoing Skytap infrastructure issues
- Check for emails from email@example.com or firstname.lastname@example.org
Other possible causes:
If recent activity (auditing) in the Skytap environment does not show an indication of the VMs having been intentionally powered off or suspended by a user, it is very likely that the guest OS initiated the shutdown, whether it is by sleep/hibernation, or an issue within the operating system (e.g. blue screen of death). To investigate this further, in-guest events/logging are a good starting point.
"Why was my VM shut down or suspended?": https://help.skytap.com/troubleshooting-why-did-my-vm-suspend-or-shut-down.html
"Viewing recent activity for an environment": https://help.skytap.com/environment-activity.html
"Automatically shut down or suspend inactive environments": https://help.skytap.com/auto-shutdown.html
"Viewing the Skytap Health Dashboard": https://help.skytap.com/status.html
Article is closed for comments.