In VirtFusion, packages are the templates behind every VPS plan you sell. A package fixes the CPU, memory, disk, traffic and network limits, so servers created from it are consistent and WHMCS only has to pass the package ID.
Before you start
- At least one hypervisor added and working (add a hypervisor).
- Storage configured on the hypervisor so the package can target it.
- A clear plan table: names, resources and what you will charge in WHMCS.
Plan your VirtFusion packages
| Example plan | vCPU | RAM | Disk | Traffic |
|---|---|---|---|---|
| VPS-1 | 1 | 2 GB | 40 GB | 2 TB |
| VPS-2 | 2 | 4 GB | 80 GB | 4 TB |
| VPS-4 | 4 | 8 GB | 160 GB | 8 TB |
These figures are only an example layout; choose resources that match your hardware and overselling policy.
Create a package
- Log in to the VirtFusion admin area and open Packages.
- Click to create a new package and give it a clear name (customers may see it).
- Set CPU cores and, if you use it, the CPU share or limit to stop one VPS taking a whole core.
- Set Memory in MB and the primary disk size in GB.
- Choose the storage profile or type so the disk lands on the right backend (local, LVM or ZFS).
- Set traffic (monthly bandwidth) and the network speed limits for inbound and outbound traffic.
- Set disk I/O limits if you want to protect neighbours from heavy disk users.
- Save the package and note its package ID; WHMCS uses it.
Note: Changing a package normally affects new servers. Existing servers keep their resources until you resize or change their package.
Connect packages to WHMCS
- In WHMCS create a product using the VirtFusion module.
- Enter the VirtFusion package ID and the hypervisor group in the module settings.
- Add configurable options for OS choice or extra IPs if you offer them.
The full module setup is covered in VirtFusion WHMCS module setup.
Check afterwards
- Create a test server from the package and confirm CPU, RAM and disk inside the VPS (
nproc,free -m,lsblk). - Run a quick speed test to confirm the port limit.
Troubleshooting
- Server creation fails with no capacity: the hypervisor group has no node with enough free RAM or disk for the package.
- Wrong storage used: check the storage profile on the package and on the hypervisor.
Frequently asked questions
Can one package be used on several hypervisors?
Yes. The package defines resources; the hypervisor group decides where servers are placed.
How do I offer an upgrade?
Create the larger package, then use WHMCS upgrades or resize the server in the admin area.
Should package names match WHMCS product names?
It is not required, but matching names makes support much easier.