Skip to main content
Version: Next

FAQ

The firewall feature blocks connectivity to other VMS​

This issue is usually caused by the UFW firewall on the hypervisor. The fix is pretty simple with a one time only command.

ufw default allow routed

Re-commissioned but receiving the error commission status done​

This happens when the hypervisor has already been locked to a control server. Usually the hypervisor should be re-installed as it may contain files or even virtual servers which may conflict if you add it to a new control server.

If you are sure the hypervisor is clean, you can remove the file /opt/virtfusion/app/hypervisor/conf/auth.json to allow it to be re-linked.

Hybrid Migration has Stalled​

Sometimes you may run in to a situation where connectivity is lost between hypervisors when migrating a server. In this situation, you can manually restart the migration.

  • Navigate to the list of migrations (Server -> Migrations).
  • Find the migration that has stalled and click on the log icon at the end of the row.
  • Scroll down to the section called Commands.
  • Take the first command listed and run it via SSH on the control server. it will look similar to /opt/virtfusion/php/bin/php /opt/virtfusion/app/control/artisan server:migrate-v2 virtfusion-migrate-v2-id=1234
  • Wait for it to complete. It may take a while.

I receive error: Unable to get index for interface eth0: No such device when booting a server​

You will receive this error if you are attempting to use MacVTap networking and the interface is specified incorrectly under the hypervisor network settings.

Find the name of your primary interface using ip a on the hypervisor and update Hypervisor -> Networks -> Primary Network -> Interface Name with the correct name.

Updating Supervisor on the Control Server​

Follow the instructions below for you control server Linux distribution. All commands should be run in SSH as root.

Important

Before reloading Supervisor. Make sure there are no server tasks running.

Debian/Ubuntu​

wget https://install.virtfusion.net/debian-supervisord.conf -O /etc/supervisor/supervisord.conf
supervisorctl reload

RHEL​

wget https://install.virtfusion.net/rhel-supervisord.conf -O /etc/supervisord.conf
supervisorctl reload

priority.xml found​

You may encounter this error during certain actions if a disaster recovery session is currently running. Additionally, this error can also appear if a disaster recovery process has failed on a specific server.

If you are certain that the disaster recovery process is no longer running, you should attempt to restart it for the specific server. You can do this using the following command.

vfcli-hv dr:backup --only-servers=SERVER_ID

You should replace SERVER_ID with the appropriate numeric ID for the server.

How do i enable nested virtualization​

Nested virtualization is enabled by default if a virtual server uses the host-passthrough CPU model. You may disable nested virtualization by toggling the appropriate extra CPU flags (svm/vmx) to disable.

Disabling QEMU Sandbox​

Why you should not disable this:

  • Protects the host from potentially compromised VMs.
  • Adds an additional layer of defense in multi-tenant environments.
  • Helps meet security/compliance standards in datacenters.

If you still want to disable sandboxing, run the following commands on the hypervisor:

sed -i "s/#seccomp_sandbox = 1/seccomp_sandbox = 0/g" /etc/libvirt/qemu.conf
systemctl restart libvirtd

You receive a 500 internal server error after updating MariaDB​

Sometimes, MariaDB release breaking changes. You can install our latest configurations by running the following commands on your control server:

Debian & Ubuntu​

wget https://install.virtfusion.net/my.cnf -O /etc/my.cnf
systemctl restart mariadb
vfcli app:restart --services=fpm,web,queue-hard

RHEL​

wget https://install.virtfusion.net/my-rhel.cnf -O /etc/my.cnf
systemctl restart mariadb
vfcli app:restart --services=fpm,web,queue-hard

I receive a 401 error when connecting to a hypervisor​

A 401 Unauthorized error indicates an authentication issue between the control server and the hypervisor.

One common reason for this is that the IP address of the control server has changed. The hypervisor uses this as part of the authentication process.

Edit /opt/virtfusion/app/hypervisor/conf/auth.json on the hypervisor and edit the "ip" field to reflect the new IP address of the control server.

Example:

{
    "ip": "NEW_IP_HERE",
    "token": "CqlsVq6zS4vwLQEZqlVo5tHmkgBzvdZYQ2NJnr5q...",
    "hash": "bc1a53dd974e54c903399fcbe8d05550b35842ca052bc5...",
    "id": 6
}
important

Do not edit or make any changes to the token, hash, or id fields as this will invalidate all the authentication and a re-commission will be required.

Server console previews are not working​

Console previews require ImageMagick installed on a hypervisor. With older installations of VirtFusion this package may be missing and will need installing.

RHEL

dnf install ImageMagick

Debian/Ubuntu

apt install imagemagick
Last updated on