Page Comparison

Not Allocated

Image Removed

Image Added

The VM does not exist on the cloud node; it is just a template of the VM to be deployed and it only exists in Abiquo. The physical machine and other resources are not allocated in the cloud node and it is not consuming resources. For  
For example, if you add a VM template to a virtual appliance with a VM that is deployed, the VM you just created is not deployed and its state is not allocated. If you undeploy a virtual appliance, then all the VMs in the virtual appliance will be undeployed, and these VMs will be in the not allocated state.

Allocated

The VM does not exist on the cloud node but a physical machine or provider has been assigned to it. When you deploy a VM, the first step in the deploy process is the resource scheduling or allocation. After resource allocation, the VM is in the allocated state.
This state is usually a short step in the deploy process.

Configured

The VM exists on the cloud node. Resources such as network and volumes are allocated to it on the physical machine or in the provider. After the VM is configured in the hypervisor or provider, the VM is in the configured state.
This state is usually a short step in the deploy process.

On

Image Removed

Image Added

The final step in the deploy process is to power on the VM.
A VM in the on state is exists in the cloud node and is running. 

Paused

Image Removed

Image Added

The VM exists on the cloud node and the VM is suspended.

Off

Image Removed

Image Added

The VM exists in the cloud node but it is not running.
Resources are still allocated in the cloud node.

Locked

Image Removed

Image Added

An operation is being performed on the VM.
The status bar shows LOCKED but it is covered by the progress notification. VMs awaiting workflow review will be locked with the progress notification "Waiting to be reviewed"

Unknown

Image Removed

Image Added

The platform does not have information about the current state of the VM but the machine exists on the cloud node.  VMs may be put in the UNKNOWN state if there is an issue with a connection to the hypervisor or provider, .
To delete a VM in the unknown state, you need the "Delete unknown virtual machine" privilege and also access to the enterprise or the "Administer all enterprises privilege". The platform does not display VMs in the UNKNOWN state and their resources on the dashboard and it does not count them in allocation limits for CPU, RAM, and storage.

Maintenance

Image Removed

Image Added

The administrator can lock or protect a VM for maintenance when it is in any of the deployed states of on, paused, or off. See Protect a VM

Off - Deallocated

The VM exists in Azure but it is deallocated. This means:

1. It is powered off

2. It is not consuming any CPU or RAM costs in Azure

3. It does not have any IP addresses assigned to it in Azure

The deallocated state is not an Abiquo VM state, but Abiquo recognizes this state in an Azure VM after a hard power off. A VM in the deallocated state will have the "deallocated" attribute set to "true".