Boomerang deploy failure causes.
Boomerang virtual machine deploy fails. This generally presents as failure due to timeout.
It is not possible to understand exactly why a given virtual machine is not booting up. The following are things we have found to cause deployment failure:
The Windows virtual machine has Hyper-V configured. AWS/Azure do not support nested virtualization and Hyper-V machines will bootloop with crashes without hardware virtual support.
Your virtual machine has a hard disk on the IDE controller. Move the disk to a different controller and replicate a new snapshot to resolve this.
Boomerang gathers information from vSphere to determine whether a VM is supported by AWS or not. Boomerang is designed to be non-intrusive and we do not look into your VMs for additional information. As a result, certain incompatibility issues can only be detected after a “Deployment” action. We strongly recommend our users to test their recovery plan (deployment) on a regular basis.
For AWS, sometimes a deployment failure cause can be ascertained by querying Amazon as follows:
- Install the AWS CLI: https://aws.amazon.com/cli/
- Run "aws configure" and enter the appropriate credential and region information
- Run "aws ec2 describe-import-image-tasks --import-task-id import-ami-xxxxxxx". Your task id can be found in the deployment details.