FortiOS 7.4.x introduced several innovations. Build 2731 (specific to 7.4.7) likely includes:
<cpu mode='host-passthrough' check='none'/> <memoryBacking> <hugepages> <page size='1048576' unit='KiB'/> </hugepages> </memoryBacking>
virt-install \ --name=FGT-v747-Mure \ --vcpus=2 \ --memory=4096 \ --disk path=/var/lib/libvirt/images/fortigate/fgt_boot.qcow2,format=qcow2,bus=virtio \ --disk path=/var/lib/libvirt/images/fortigate/fgt_log.qcow2,format=qcow2,bus=virtio \ --network bridge=br0,model=virtio \ --network bridge=br1,model=virtio \ --os-variant=generic \ --graphics none \ --console pty,target_type=serial \ --import Use code with caution. Importing into GNS3 Network Simulation Labs
sudo virsh console FGT-VM-747
You can now access the graphical user interface (GUI) by navigating to https://192.168.1.99 in your web browser to upload your enterprise license certificate file.
If you are deploying via Linux CLI using virt-install , you can use a deployment command similar to this:
Indicates a "Maintenance" release built primarily for stability and bug corrections, as opposed to an "F" feature-heavy release. fgtvm64kvmv747mbuild2731fortinetoutkvmqcow2
For staging complex multi-vendor network maps, this exact .qcow2 file is highly sought after for GNS3 integration platforms .
If you have the file fgtvm64kvmv747mbuild2731fortinetoutkvmqcow2 , here’s how to deploy it on a Linux KVM host:
config system interface edit port1 set mode static set ip 192.168.1.99 255.255.255.0 set allowaccess ping https ssh http next end Use code with caution. FortiOS 7
virt-install \ --name FortiGate-v7.4.7 \ --description "FortiGate NGFW Virtual Appliance" \ --os-variant=rhel8.0 \ --ram=2048 \ --vcpus=2 \ --disk path=/var/lib/libvirt/images/FGT_VM64_KVM-v7.4.7.M-build2731-FORTINET.out.kvm.qcow2,bus=virtio \ --disk size=30,bus=virtio \ --network bridge=br0,model=virtio \ --network bridge=br1,model=virtio \ --graphics none \ --import Use code with caution.
Licensing is based on throughput or VM instance type (e.g., FG-VM01 to FG-VM-UL).