VF VirtFusion Documentation
বাংলা

VirtFusion Documentation#

The full path to a VPS business with VirtFusion — 7 phases, 54 lessons. It starts at installation and ends at API automation and the customer panel.

What is in this documentation#

FileSubjectWho it is for
01-concepts.mdPhase 1 — What it is, and how it fits together (6 lessons)Everyone
02-installation.mdPhase 2 — Installation (7 lessons)Administrators
03-network-storage.mdPhase 3 — Network and storage (8 lessons)Administrators
04-administration.mdPhase 4 — Daily administration (11 lessons)Administrators
05-api.mdPhase 5 — API and integration (9 lessons)Developers
06-customer-panel.mdPhase 6 — The customer panel (7 lessons)End customers
07-operations.mdPhase 7 — Operations and comparison (6 lessons)Administrators

Where to start#

If you are a new provider, read phases 1, 2, 3, and 4 in that order. If the system already runs, you can start at phase 4.

Who you areReading order
A new hosting provider1 → 2 → 3 → 4 → 7
A developer (billing or automation)1 → 5
A support team1 → 6 → 7
Someone who comes from Proxmox1 → 7.5 (the comparison) → 2

VirtFusion at a glance#

VirtFusion is a KVM virtualization control panel for hosting providers. It is not a hypervisor itself. It drives Linux KVM and libvirt. On top of them it gives a panel, a billing connection, and an API, for the provider and for the customer.

SubjectValue
Current stable version7.x
HypervisorKVM (libvirt and QEMU)
Control server OSDebian 12/13, Ubuntu 22.04/24.04, AlmaLinux 9/10, Rocky 9/10
Hypervisor architecturex86_64, and AArch64 (Debian 12/13, Alma 10, Rocky 10)
LicenceOne key for each cluster, with a VM limit for each hypervisor
APIREST, at /api/v1, with a Bearer token
Billing integrationWHMCS, Blesta, Clientexec, BillingServ, HostBill, Paymenter, Upmind

Learn these three words first#

  • Control server — where the panel, the database, and the API run. One

cluster has exactly one.

  • Hypervisor — the bare-metal machine that runs the real VMs. You can add

as many as you want.

  • Package — a plan of CPU, RAM, disk, and traffic. A server is always made

from a package.

The other words are in phase 1, lesson 3.