VirtFusion Troubleshooting: Fix Common Errors

This VirtFusion troubleshooting guide collects the problems providers hit most often and the checks that solve them. Work from the outside in: is the control server healthy, can it reach the hypervisor, and is KVM working on the node?

Before you start

Root SSH access to the control server and the affected hypervisor.
IPMI or console access to the hypervisor in case networking is the problem.
The server ID, hypervisor name and time the problem started.

Hypervisor shows offline

From the control server, test connectivity: ping HYPERVISOR_IP and ssh root@HYPERVISOR_IP.
Check that a firewall change has not blocked the ports VirtFusion uses between the two.
On the hypervisor, confirm libvirt is running: systemctl status libvirtd.
Check disk space: df -h. A full root filesystem stops services.

Server build or task is stuck

Open the task or queue view in the admin area and read the error message.
Make sure the OS template exists and could be downloaded to that hypervisor.
Check the storage backend has free space (vgs for LVM, zpool list for ZFS).
Make sure the control server's background queue workers are running; restart them as described in the VirtFusion documentation if tasks never start.

VPS has no network

Confirm the IP is assigned to the server and the block's gateway and netmask are correct.
On the hypervisor, check the bridge: ip -br link and bridge link should show the VM's interface attached to br0 (or your bridge).
Inside the VPS (via VNC), check ip a and ip r. A missing default route usually means the template did not apply network settings.
Ask your upstream whether the IP block is routed to the hypervisor's main IP or needs MAC addresses registered.

More detail is in hypervisor networking and IP blocks.

WHMCS provisioning fails

Open WHMCS → Configuration → System Logs → Module Log and read the VirtFusion request and response.
401 or unauthorised: the API token is wrong, expired or revoked.
Package or group not found: the IDs in the product's module settings do not match VirtFusion.
No capacity: no hypervisor in the group has free resources or IPs.

VNC console does not open

The server must be running for a live console.
Browser extensions or a strict firewall can block the WebSocket connection; try a private window.
Check the hypervisor is reachable on the console ports listed in the documentation.

Panel errors after an update

Clear your browser cache and log in again.
Check the control server logs and free disk space.
Re-run the update command if it was interrupted; see update VirtFusion.

Frequently asked questions

Where are VirtFusion logs?

Task errors show in the admin area; system logs are on the control server and hypervisor (the documentation lists the paths for your version).

Will restarting libvirt stop running VPSs?

Restarting libvirtd normally does not stop running guests, but avoid doing it during busy hours.

When should I contact VirtFusion support?

When a task fails with an internal error after you have checked connectivity, storage and logs.

Next steps

Was this guide helpful?

Still stuck?

Ask MdmHost AI for a quick answer, or open a ticket and our team will take a look. We are here 24/7.

Ask MdmHost AI Open a ticket