: Virtual images like the one described can also be used for disaster recovery solutions or for testing configurations in a controlled environment.
| Component | Meaning | |:---|:---| | | FortiGate Virtual Machine, 64-bit architecture (x86_64). | | KVM | Target hypervisor (Kernel-based Virtual Machine for Linux systems). | | v723f | Major firmware version v7.2.3 build (the "f" may indicate a final build or specific firmware flavor). As of 2022, v7.2.3 was the latest KVM release. | | build1262 | Specific internal build number (1262) for the FortiOS firmware. | | FORTINET.out.kvm | Standard naming format for a "new deployment" image (not an upgrade package). | | qcow2 | QEMU Copy-On-Write v2 disk format, the native KVM/QEMU virtual hard drive image. |
The suffix new likely indicates the user found an updated build of the same version branch, a freshly downloaded package, or a new attempt to spin up the environment. fgtvm64kvmv723fbuild1262fortinetoutkvmqcow2 new
| Component | Interpretation | |-----------|----------------| | fgtvm64 | FortiGate Virtual Machine for 64-bit architecture | | kvm | Hypervisor type – KVM (Linux native virtualization) | | v723f | FortiOS version 7.2.3 (the ‘f’ may indicate a patch or specific branch) | | build1262 | Internal build ID – specific compiled version | | fortinet | Vendor – Fortinet Networks | | outkvmqcow2 | Output format: KVM-compatible QCOW2 disk image | | new | Indicates a recent release or updated artifact |
Modify the interface properties to match your local subnet configuration: : Virtual images like the one described can
: Describes the file format as QCOW2 , which is optimized for KVM/QEMU environments . Key Specifications for This Version
fgtvm64-kvm-v7.2.3-fbuild1262-fortinet-out-kvm.qcow2 | | v723f | Major firmware version v7
Native drivers mapped for VirtIO, supporting Single Root I/O Virtualization (SR-IOV) and Data Plane Development Kit (DPDK) for microsecond packet handling across virtual interfaces. Virtual Machine Allocation Requirements
Your target (Proxmox VE, raw Virt-manager, or GNS3/EVE-NG?)
: Pin dedicated physical execution cores directly to the FortiGate VM process to minimize CPU cache thrashing on busy KVM host machines.
Inside the destination folder, you will find fortios.qcow2 alongside deployment templates. Rename it to a deployment-specific title to prevent overwriting: