Support and News Forum

Hello support,

I am following the below link in order to add a Fortinet FW image.

The file I am using is: FOS_VM64-v5-build1167-FORTINET.out.ovf

The procedure I am following is option 2) in: http://www.eve-ng.net/index.php/documen ... net-images

In the procedure:
2.5. Convert original vmdk files to qcow2 format
qemu-img convert -f vmdk -O qcow2 fmg.vmdk virtioa.qcow2
qemu-img convert -f vmdk -O qcow2 datadrive.vmdk virtiob.qcow2

What I get:
root@eve-ng:/opt/unetlab/addons/qemu/fortinet-FMG-v5.4-build1167# unzip FOS_VM64-v5-build1167-FORTINET.out.ovf.zip
Archive: FOS_VM64-v5-build1167-FORTINET.out.ovf.zip
inflating: datadrive.vmdk
inflating: FortiOS-VM64.ovf
inflating: FortiOS-VM64.hw07_vmxnet3.ovf
inflating: fortios.vmdk
root@eve-ng:/opt/unetlab/addons/qemu/fortinet-FMG-v5.4-build1167#

What is the reason why the names in the procedure, and the ones I am getting do not match?
Does datadrive.vmdk have to be virtiob.qcow2?
And does fortios.vmdk have to be virtioa.qcow2?

Are these instructions, in this order correct?

qemu-img convert -f vmdk -O qcow2 fortios.vmdk virtioa.qcow2
qemu-img convert -f vmdk -O qcow2 datadrive.vmdk virtiob.qcow2

Thanks

what is this inflating output doing

root@eve-ng:/opt/unetlab/addons/qemu/fortinet-FGT-v5-build1547# ls
FGT_VM64-v5-build1547-FORTINET.out.ovf.zip
root@eve-ng:/opt/unetlab/addons/qemu/fortinet-FGT-v5-build1547# unzip FGT_VM64-v5-build1547-FORTINET.out.ovf.zip
Archive: FGT_VM64-v5-build1547-FORTINET.out.ovf.zip
inflating: datadrive.vmdk
inflating: FortiGate-VM64.ovf
inflating: FortiGate-VM64.hw04.ovf
inflating: FortiGate-VM64.vapp.ovf
inflating: FortiGate-VM64.hw07_vmxnet3.ovf
inflating: fortios.vmdk

I seriously recommend get KVM image not vmdk....
in how to I used KVM original image for FGT

but vmdk was used for forti manager

Got it working using the KVM image, thanks.