Abiquo Documentation Cookies Policy

Our Documentation website uses cookies to improve your experience. Please visit our Cookie Policy page for more information about cookies and how we use them.

Abiquo 2.6

Skip to end of metadata
Go to start of metadata


In the Abiquo GUI the term persistent is used instead of stateful to better reflect the nature of these virtual machines. The term virtual machine template has replaced virtual image to describe a virtual machine's disk and definition.

Secondary Hard Disks on the Hypervisor Datastore Are Not Persistent

Secondary hard disks on the hypervisor datastore will always be deleted when a persistent virtual machine is undeployed.

Introduction to Persistent Virtual Machines

By default, Abiquo deploys virtual machine templates from the Apps Library to the target physical infrastructure. Every time you deploy a virtual appliance, Abiquo copies the templates from the Apps Library to the hypervisor with the specific virtual appliance configuration. When you undeploy a virtual appliance, all changes made to the system volumes of the virtual machines are lost. This is because the next time you deploy the virtual appliance, the template files will be copied again from the Appliance Library to the hypervisor to create new system disks. Persistent virtual machines solve this problem because the persistent virtual machine is stored on an external volume, so all information will be persistent on the target storage device. Persistent virtual machines will boot directly from the external volume.

See Saving Changes to Virtual Machines.


Before you can create persistent virtual machines, you must:

Creating Persistent Virtual Machine Templates

Before you create a persistent virtual machine, you must create a persistent virtual machine template in the Virtual Appliance screen. See Manage Persistent Virtual Machine Templates

Creating Persistent Templates from the VApp Screen

You can create persistent templates from inside a VApp on the Persistent Virtual Machine Templates tab. Click the add button  at the bottom of the tab to create a new persistent template.

You can also manage your persistent virtual machine templates from the Persistent Virtual Machine Templates tab in virtual datacenters view.


Persistent Virtual Machines

Adding a Persistent Template to a Virtual Appliance

Drag and drop a persistent template to your virtual appliance. It will now be removed from the Persistent Virtual Machine Templates panel because persistent templates can only be used in one virtual appliance at any time.

Deploy a Virtual Appliance with a Persistent Virtual Machine

Deploy the persistent virtual appliance by clicking the Deploy button.


Persistent Virtual Machine Icon

Persistent virtual machines are marked with the persistent icon in the form of a hard disk:


Sharing Persistent Virtual Machines

Persistent virtual machine templates  can only be used in ONE virtual appliance  at a time, to avoid concurrent modifications to the virtual machine.

Because persistent VM templates cannot be shared, they do not appear in the Appliance Library View. To share a persistent virtual machine template, deploy a persistent virtual machine and create an  instance , which will be available for deployment in other virtual machines.

Reusing Persistent Templates

When a persistent virtual machine is deleted from the virtual appliance, the template remains on the volume on the storage device.

This means that the persistent virtual machine template will appear in the Persistent Virtual Machine Templates tab again and it may be re-used in other virtual appliances:

Deleting Persistent Virtual Machines

When you click the delete button to remove a persistent virtual machine from your virtual appliance, the persistent template will not be deleted from the storage volume. It will be available in your virtual datacenter for reuse in another virtual appliance.

To delete the persistent virtual machine template, go to the Persistent Virtual Machine Template tab in Virtual Datacenters view.