# Copy image to default storage pool
sudo cp fgtvm64kvmv747mbuild2731fortinetoutkvmqcow2 /var/lib/libvirt/images/fortigate.qcow2
Add to VM's XML:
<qcow2encryption format='lUKS'/>
<blockio logical_block_size='512' physical_block_size='4096'/>
FortiGate firmware follows semantic versioning: v7.4.7 indicates major release 7, feature release 4, patch release 7. Build number 2731 is an internal build identifier. fgtvm64kvmv747mbuild2731fortinetoutkvmqcow2 new
The string fgtvm64kvmv747mbuild2731fortinetoutkvmqcow2 new breaks down into several critical technical identifiers. Understanding each part is essential before deployment: # Copy image to default storage pool sudo
| Token | Meaning |
|-------|---------|
| fgt | FortiGate |
| vm64 | Virtual Machine, 64-bit architecture |
| kvm | Kernel-based Virtual Machine (hypervisor) |
| v747m | Version 7.4.7, possibly 'm' for mature or maintenance release |
| build2731 | Internal build number (2731) — often tied to patch level |
| fortinet | Vendor |
| out | Possibly "out-of-tree" or external release |
| kvm | Repeat confirmation of hypervisor target |
| qcow2 | QEMU Copy-On-Write version 2 disk image format |
| new | Fresh or untampered image | FortiGate firmware follows semantic versioning: v7
Interpretation: You are dealing with a FortiGate VM for KVM, version 7.4.7, build 2731, packaged as a .qcow2 image. This is likely a firmware release from Fortinet’s late 2024 or early 2025 cycle.
FortiOS 7.4 matures the ZTNA offering, converging security for both private and public clouds.
qemu-img info FGT_VM64_KVM-v7.4.7-build2731-FORTINET.out.kvm.qcow2
qemu-img resize FGT_VM64_KVM-v7.4.7-build2731-FORTINET.out.kvm.qcow2 +20G
# Convert if needed (though already qcow2)
cp fgtvm64kvmv747mbuild2731fortinetoutkvmqcow2 /var/lib/libvirt/images/fgt.qcow2