When you download the KVM-specific firmware from the Fortinet Support Portal, you receive a package containing the fortios.qcow2 file. This image contains the entire FortiOS operating system, pre-configured to boot in a virtualized environment. Key Use Cases
virt-install \ --name FortiGate-VM \ --ram 2048 \ --vcpus=2 \ --import \ --disk path=/path/to/fortios.qcow2,format=qcow2,bus=virtio \ --network bridge=virbr0,model=virtio \ --graphics none \ --console pty,target_type=serial fortios.qcow2
qemu-img info fortios.qcow2
To run FortiOS via a QCOW2 image, your environment typically requires: QEMU/KVM, Proxmox, or Nutanix AHV. CPU: Minimum 1 vCPU (2+ recommended for production). RAM: Minimum 1GB (2GB+ for features like SSL Inspection). When you download the KVM-specific firmware from the
While specific steps vary by hypervisor, the general virtual hardware requirements for a stable environment include: Fortigate - Forti Stacks - Read the Docs CPU: Minimum 1 vCPU (2+ recommended for production)
. But for those who live in the world of virtualization, the real magic happens inside a single, unassuming file: fortios.qcow2