Yes. Proxmox uses KVM under the hood. Rename the file to fmg.qcow2 , create a VM, and import the disk as a SCSI or VirtIO Block device.
To ensure a successful setup, verify the following against the official KVM Administration Guide : :
Once the hardware settings and disks are in place, power on the VM. Connect to its console to complete the initial setup, which includes configuring the IP address, gateway, DNS, and setting the administrator password.
The feature aims to streamline the deployment, configuration, and management of FortiGate VM64 instances on KVM hypervisors. This includes developing a user-friendly interface or toolset that automates the process of:
If you prefer a Graphical User Interface (GUI), you can deploy Build 1183 using Virtual Machine Manager ( virt-manager ). Step 1: Prepare the Storage Pool Fmg-vm64-kvm-v6-build1183-fortinet.out.kvm.zip
: The official branding and validation tag from the vendor.
. This specific build (1183) is designed for deployment on Kernel-based Virtual Machine (KVM) environments. File Overview FortiManager VM64 Build Number: KVM (Kernel-based Virtual Machine) f78c893f30478de89c7e94792f6800f7 Approximate Size: Deployment Summary
: Unzip the archive to access the .qcow2 disk image files.
Before extracting and deploying Build 1183, the hypervisor node must meet or exceed minimum resource envelopes to prevent execution instability or out-of-memory kernel panics. Hardware Allocations Resource Dimension Minimum Baseline Recommended Production 4 to 8+ vCPUs (dependent on managed device count) System Memory (RAM) 8 GB to 32 GB (highly scalable per node load) Primary Storage (OS) 8 GB (fixed virtual operating disk size) Secondary Storage (Data) 500 GB to 4 TB+ (allocated for logging/databases) Network Interfaces 1 Virtual NIC 2 to 4 vNICs (for isolated management/logging paths) Supported KVM Environments Red Hat Enterprise Linux (RHEL) / CentOS KVM Hypervisors Ubuntu LTS with qemu-kvm and libvirt Proxmox Virtual Environment (PVE) Nutanix AHV (Acropolis Hypervisor) 3. Package Content Disassembly To ensure a successful setup, verify the following
| Use Case | Description | |----------|-------------| | | Validate policy workflows before pushing to production firewalls. | | Air-gapped environments | On-prem KVM clusters with no internet – requires offline deployment from a zip file. | | Legacy compatibility | Some older FortiGate models (e.g., 60D, 100D) require FortiManager v6.x for feature parity. | | CI/CD pipeline for network automation | Spin up ephemeral FMG instances inside Jenkins/KVM runners for Ansible or Terraform testing. |
To run version 6.2.2 reliably in production, you must fulfill the foundational resource requirements: File FAZ_VM64_KVM-v6-build1183-FORTINET.out.kvm.zip
: Represents major version 6 of the FortiManager operating system.
Unpack the .zip archive on your management workstation or directly on the KVM host using the command line: unzip Fmg-vm64-kvm-v6-build1183-fortinet.out.kvm.zip Use code with caution. This extraction yields two vital virtual disk files: fortios.qcow2 : The operating system and boot drive. : Upon first boot
: Indicates that the software is engineered for a 64-bit virtual machine architecture.
: Upon first boot, the CLI is used to configure basic networking ( IP address
: The specific engineering build number (associated with v6.2.3).
When you download and extract the .zip archive from the official Fortinet Customer Service & Support Portal, it reveals the primary disk image file:
: Push configuration changes, firmware updates, and SD-WAN policies across the network. Role-Based Access
Before extracting the ZIP archive and launching the virtual appliance, ensure your KVM host meets the following minimum resource allocations for FortiManager VM64: Hardware Allocations Minimum 2x vCPUs (Virtual CPUs).