Why was my VM shut down or suspended?
A VM may be automatically shut down or suspended if:
The environment was not in use.
The environment-wide auto-shutdown options shut down or suspend all of the VMs in an environment after a period of inactivity. For more information, see How auto-shutdown works. To check or change the auto-shutdown options for an environment, see Enabling auto-shutdown for an environment.
The VM is configured to sleep or shut down after a period of inactivity.
- If the guest OS power options put the computer to sleep after a period of inactivity, the VM power state in Skytap changes to Suspended.
- If the guest OS power options automatically shut down the computer, the VM power state in Skytap changes to Powered off.
The VM was in use, but it was being used over a published service or public IP connection.
The environment-wide auto-shutdown options feature doesn’t monitor published services or public IP addresses for user activity in the VMs. For example, auto-shutdown may recognize a VM as inactive, even when it’s being used via RDP or SSH connections over published services.
To prevent a VM from automatically shutting down or suspending while published services or other unmonitored services are in use, run a script that periodically sends keep-alive messages to Skytap. For instructions, see Sending keep-alive messages from a VM to prevent auto-shutdown.
The environment was copied or saved as a template.
VMs are automatically suspended during these actions. The environment may have been copied or saved by an automated script, schedule, or another user.
To further investigate why a VM was shut down or suspended, view the recent environment activity, or work with a Skytap administrator within your organization to review the Skytap auditing report.