From internal discussions in KVM-focused security forums, here are known quirks for build 1262:

| Issue | Solution | |-------|----------| | VM crashes after snapshot restore | Use virsh snapshot-revert --force | | VirtIO network driver drops packets | Set mtu=9000 on both host bridge and FortiGate interface | | Web GUI slow on QCOW2 | Convert raw disk (qemu-img convert -O raw) for production | | “Invalid license” after reboot | Ensure system time sync (NTP) before license check |

  • To check license: 
    get system status
show system license
  • To upload a new license: 
    execute license upload <ftp/tftp/path>

    • If it fails to boot due to licensing, you may need a Fortinet support contract or a trial license from the Fortinet website.

    execute restore config tftp <filename.lic> <tftp-server-ip>

    After reboot, the limited evaluation mode disappears.

    This guide provides a general overview. Specific steps, especially for configuring the FortiGate services and network settings, should be referenced from Fortinet's official documentation due to the proprietary nature of these configurations.

    This evaluation build typically operates in "Trial Mode" upon deployment.

    Isolate physical cores to reduce latency in packet processing.

    A probable original command might resemble:

    qemu-img create -f qcow2 fgtvm64-kvm-v723f-build1262-fortinet.qcow2 20G
virt-install \
  --name fgtvm64_exclusive \
  --vcpus 4 --memory 4096 \
  --disk path=fgtvm64-kvm-v723f-build1262-fortinet.qcow2,format=qcow2 \
  --import \
  --os-variant generic \
  --features kvm_hidden=1 \
  --cpu host-passthrough \
  --exclusive

    You can create a VM using the virt-install tool or the virt-manager GUI.