Business process manager and V2V troubleshooting

The Abiquo Business Process Manager / V2V Conversion Services server is used to convert VM templates from one disk format to another.
This server performs conversions when you create an instance, add an image, and so on.

What processes run on the BPM / V2V Server?

The server has two main modules: v2v-diskmanager and mechadora.

v2v-diskmanager performs format conversions
mechadora performs dumps to volumes and reads from volumes and disks.

The v2v-diskmanager uses two utilities to convert templates: qemu and vBoxManageSVC.

When does the business process manager / V2V conversion manager run?

It runs for conversions from one template format to another, when loading a new template and when conversions are requested by the v2v-diskmanager module.

Possible issues with the BPM and V2V Server

All of the following indicate problems with the V2V Conversion Services.

I created a datacenter and added the remote services, including the Business Process Manager/V2V machine. Why does the remote service check give a red light for BPM/V2V?
Why didn't my conversion work?
Why wasn't my instance template created?

You should perform the checks given below.

Where does Abiquo store the V2V conversions?

The working folder for V2V Conversions is /opt/abiquo/v2v-conversions.

The completed conversions are stored in the catalogue in the formats folder.

Check a V2V conversion that is in progress

Using ps

If a conversion is in progress, the v2v-diskmanager and mechadora processes will be running. You can check them with the following commands.

Check the v2v-diskmanager process is running - see Service Management#v2v-diskmanager: ps aux | grep v2v

Check the mechadora process is running with ps aux | grep mechadora

Using top

If a conversion is in progress and you are running top, you will see the following:

qemu
vBoxManageSVC

Check configuration properties in the V2V server properties file

The V2V properties are shown in the following sample file (by default this is: /opt/abiquo/config/examples/abiquo.properties.v2v)

Sample abiquo.properties on V2V Server

[remote-services]
abiquo.rabbitmq.host = <RabbitMQ-Server-IP>
abiquo.rabbitmq.port = 5672
abiquo.rabbitmq.username = guest
abiquo.rabbitmq.password = guest
abiquo.datacenter.id = Abiquo

You should set abiquo.rabbitmq.host to the IP address of the RabbitMQ Server. The default is the Abiquo Server.
The abiquo.datacenter.id should be a unique value for each datacenter and the same value as for the Remote Services server.
The other values should be set to appropriate values for your installation of RabbitMQ. You do not need to change these values for a default installation.
See Abiquo configuration properties

Check that NFS repository is mounted on the V2V Server

Yes, the NFS Repository is required on the V2V Conversion Services machine. Check that the NFS repository is mounted in the correct location. You can use the df command. The default location is /opt/vm_repository

Check the appropriate ports are open for the V2V Server

The ports and communications required for the V2V Server are listed on the main Ports and communications page. Check the V2V Server has access to the appropriate IP addresses and ports. Remember that the V2V Server requires access to RabbitMQ on the Abiquo Server.