VirtFusion hypervisor groups bundle nodes that should be treated as one pool, usually one location or one hardware class. New servers are placed on a node within the chosen group, so groups are how you offer locations and keep premium hardware separate.
Before you start
- At least one hypervisor added (add a hypervisor).
- A naming plan, for example Germany – NVMe, USA – NVMe, Singapore – Storage.
Create a VirtFusion hypervisor group
- In the admin area open the hypervisor groups section.
- Create a group with a clear name customers may see.
- Add the hypervisors that belong to it. Keep each group to one location and similar hardware.
- Save and note the group ID.
How placement works
- When a server is created in a group, VirtFusion picks a hypervisor in that group with enough free resources.
- Disable a hypervisor for new servers (maintenance or full) without removing it from the group, so existing VPSs keep running.
- IP blocks must be available on the hypervisors in each group, or creation fails even with free RAM.
Tip: Mark nearly full hypervisors as unavailable for new servers so they keep headroom for upgrades.
Offer locations in WHMCS
- Either create one WHMCS product per location, with the group ID set in module settings, or
- Add a configurable option Location whose values map to the group IDs, as supported by the module.
- Place a test order for each location and confirm the server lands in the right group.
Troubleshooting
- Server lands on the wrong node: the product points to the wrong group ID.
- No capacity in a group with free RAM: check free IPs and storage on those nodes and whether they accept new servers.
Frequently asked questions
Can a hypervisor be in more than one group?
Keep it simple: one group per hypervisor avoids confusing capacity reports.
Can customers move between locations?
Moving between groups means migrating the server; IPs usually change because blocks are per location.
Should groups match WHMCS products?
Matching names makes orders and support much clearer.