mirror of
https://github.com/apache/cloudstack.git
synced 2025-12-19 20:14:06 +01:00
22 lines
3.5 KiB
HTML
22 lines
3.5 KiB
HTML
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
|
||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.3. VM Lifecycle</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="virtual-machines.html" title="Chapter 10. Working With Virtual Machines" /><link rel="prev" href="best-practices-vm.html" title="10.2. Best Practices for Virtual Machines" /><link rel="next" href="creating-vms.html" title="10.4. Creating VMs" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.cloudstack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="best-practices-vm.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="creating-vms.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="vm-lifecycle" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="vm-lifecycle">10.3. VM Lifecycle</h2></div></div></div><div class="para">
|
||
Virtual machines can be in the following states:
|
||
</div><div class="mediaobject"><img src="./images/basic-deployment.png" alt="basic-deployment.png: Basic two-machine CloudStack deployment" /></div><div class="para">
|
||
Once a virtual machine is destroyed, it cannot be recovered. All the resources used by the virtual machine will be reclaimed by the system. This includes the virtual machine’s IP address.
|
||
</div><div class="para">
|
||
A stop will attempt to gracefully shut down the operating system, which typically involves terminating all the running applications. If the operation system cannot be stopped, it will be forcefully terminated. This has the same effect as pulling the power cord to a physical machine.
|
||
</div><div class="para">
|
||
A reboot is a stop followed by a start.
|
||
</div><div class="para">
|
||
CloudPlatform preserves the state of the virtual machine hard disk until the machine is destroyed.
|
||
</div><div class="para">
|
||
A running virtual machine may fail because of hardware or network issues. A failed virtual machine is in the down state.
|
||
</div><div class="para">
|
||
The system places the virtual machine into the down state if it does not receive the heartbeat from the hypervisor for three minutes.
|
||
</div><div class="para">
|
||
The user can manually restart the virtual machine from the down state.
|
||
</div><div class="para">
|
||
The system will start the virtual machine from the down state automatically if the virtual machine is marked as HA-enabled.
|
||
</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="best-practices-vm.html"><strong>Prev</strong>10.2. Best Practices for Virtual Machines</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="creating-vms.html"><strong>Next</strong>10.4. Creating VMs</a></li></ul></body></html>
|