If you want to experiment with FortiGate on KVM, it is safest to use a standard image from the official source. Here is a proper process: Obtain the .out.kvm.zip deployment package for your platform from the Fortinet Customer Service & Support site, extract the fortios.qcow2 file, create a new VM and import the extracted .qcow2 file, allocate at least 2 GB of RAM and 1 vCPU (and a 32 GB log disk), boot the VM and log in with the default credentials ( admin and no password), set a new password for the admin account, and note the free 15-day evaluation license is active.
: This is the "wrapper," a storage format for virtual disks that supports "copy-on-write," allowing for efficient snapshots and disk space management. The Weight of "Patched"
insmod /path/to/feature.ko
Set the bus type to VirtIO for optimal performance.
: QEMU Copy-On-Write 2 format . The native storage disk format for QEMU/KVM hypervisors. It supports thin provisioning, snapshotting, and dynamic compression. fgtvm64kvmv721fbuild1254fortinetoutkvmqcow2 patched
Map the virtual interfaces to the appropriate Linux bridges or OVS (Open vSwitch) ports.
Build 1254 is for FortiOS 7.2.1 — it was released around late 2022. That build fixed several SSL VPN memory leaks and IPsec issues. If you want to experiment with FortiGate on
: This identifies the product as a FortiGate Virtual Machine designed for 64-bit architecture.
If your deployed VM is still running build 1254, upgrading to the latest patched version is strongly recommended. The Weight of "Patched" insmod /path/to/feature