Technical Tip: FortiDeceptor fixing decoy failing to deploy error

A situation may arise where a Decoy fails to deploy on the FortiDeceptor VM.

When this occurs, first review the error message displayed for the affected Decoy.

For example, there is an error similar to: 'failed to fork vm process'.

This error is most commonly caused by nested virtualization not being enabled on the hypervisor hosting the FortiDeceptor VM.

Because the configuration steps differ between hypervisors, refer to the hypervisor vendor's official documentation for the correct procedure to enable nested virtualization.

Nested virtualization support is also listed as a minimum system requirement in the FortiDeceptor Deployment Guide:

Minimum System Requirements.

The FortiDeceptor VM has specific CPU virtualization requirements:

• Intel: Virtualization Technology (VT-x/EPT).

• AMD: AMD-V/RVI.

Additionally, both virtualization technology and 64-bit support must be enabled in the system BIOS.

Quick Troubleshooting:

1. Execute the command 'hardware-info'.
2. If the CPU flag 'vmx'/'svm' is not there, enable the virtualization related settings for FortiDeceptor VM at the host side.
3. For more information on how to get the 'hardware-info', see Troubleshooting Tip: Decoys on FortiDeceptor-VM are failing to start correctly with status 'failed to create clone'.  

Additional references:

For detailed instructions, consult the documentation for the virtualization platform:

• Proxmox Nested Virtualization
• Nested virtualization in KVM 
• Nested Virtualization in Microsoft Hyper-V