Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

VM is locked during deploy

When you are deploying a VM, it may take a very long time, and the VM may appear to be locked, but there are no messages in the logs. The cause of this problem may be a hard disk that is very large for your environment.

If you need to add a large empty disk to your VMs for application data, then the best way to do this is to add an “empty” hard disk to your VM template. After you create a VM from a template with an empty disk, you may be able to resize the empty disk. An empty hard disk should deploy more quickly than a “real disk with no data”.

See https://abiquo.atlassian.net/wiki/spaces/doc/pages/311378488/Modify+VM+template+disks#Add-an-empty-disk and VM storage.


Conversions in progress

If a template or disk operation is unable to complete due to a system issue, it may seem to be in progress indefinitely. And when you try to delete a problem disk, you may see an error such as:

VIMAGE-30: "Cannot delete virtual machine template because conversions are in progress.

In this case, you may need to delete the disk directly in the file system or change the state of the VM template internally in the platform. Please contact Support for more information.

Effectively you will put your template into the NOT_AVAILABLE state. In the UI, this is called the Deleted state.

To display deleted templates in the Catalogue:

  1. Open the Catalogue, select your datacenter and beside the datacenter name, click the round arrow Refresh button

  2. Select the option to Show deleted templates

The platform will now display the deleted templates with the red X symbol as shown in the following screenshot

 Display deleted templates in the catalogue


Error replacing a VM disk due to missing OVF file

When you try to replace a VM disk by uploading a new disk, you may get an error about a missing OVF file . This error occurs when a user created the template with the Abiquo instance feature, which copies the selected disks from a captured VM. The instance template will not have an OVF file but the process to replace a disk requires the OVF file.

If the original VM is still available, do these steps:

  1. Before you replace the disk, export the OVF file for the original VM from vCenter

  2. Add it to the VM template folder on the NFS repository.

If the original VM is not available:

  1. Use a GET request to retrieve the instance template you want to modify and its disks from the Abiquo API. Or obtain these details by editing the template in the Abiquo UI

  2. Find a similar template (ideally, with the same operating system and disk format) that was uploaded into Abiquo that has a valid OVF on the NFS repository. It would also be possible to upload a new OVA template to create an OVF file.

  3. Copy the OVF file from the uploaded template’s folder

  4. Edit the OVF file to add the the correct details for your instance template from your API

  5. Add the modified OVF file to your template’s folder

For full details of how Abiquo works with OVF files, see OVF reference and Extended OVF support and template definition


  • No labels