Deploy with virt-install example:
virt-install --name fortigate-vm \
--vcpus 2 --memory 4096 \
--disk path=/var/lib/libvirt/images/fgtvm64-kvm-v7.4.7-F-build2731-FORTINET.out.kvm.qcow2,format=qcow2 \
--import --os-variant generic
Initial access:
Post-deployment tasks:
To achieve near-bare-metal throughput (up to 10 Gbps):
Example domain XML snippet:
<cpu mode='host-passthrough' check='none'/>
<memoryBacking>
<hugepages>
<page size='1048576' unit='KiB'/>
</hugepages>
</memoryBacking>
The QCOW2 image alone is not fully functional for production without a valid FortiGate VM license (bring-your-own-license or PAYG). Unlicensed mode is limited to 1 Gbps, 3 VDOMs, 30 days trial.
Would you like:
Let’s split the string into logical components:
fgtvm64 → FortiGate Virtual Machine, 64-bit
kvm → Kernel-based Virtual Machine (hypervisor target)
v747m → Version 7.4.7, ‘m’ likely for maintenance release
build2731 → Internal build number 2731
fortinet → Vendor (Fortinet, Inc.)
out → Possibly out directory or output artifact
kvm → Repeated hypervisor context
qcow2 → QEMU Copy-On-Write version 2 disk format fgtvm64kvmv747mbuild2731fortinetoutkvmqcow2
Thus, the full expansion is:
FortiGate Virtual Machine (64-bit) for KVM, version 7.4.7, build 2731, Fortinet output (KVM), QCOW2 disk image.