Virtualizor creates a service for Virtnetwork (bridge: viifbr0) on KVM and Xen.
Virtnetwork will be required for vps network.
If you get error message similar to ‘ The viifbr0 is not started. Please run service virtnetwork start ‘ on Admin dashboard/Create vps page after fresh install of Kvm/Xen Virtualizor then you will require to start virtnetwork service.
You need to make sure the network interface file on your
CentOS server ( /etc/sysconfig/network-scripts/ifcfg-servers-interface-name ) and
on your Ubuntu server ( /etc/network/interfaces ) contain IP address, netmask and gateway entries.
For CentOS , it should look like this :
IPADDR=10.0.0.93 PREFIX=24 or NETMASK=255.255.255.0 GATEWAY= 10.0.0.1
For Ubuntu, it should look like this :
address 10.0.0.93 netmask 255.255.255.0 gateway 10.0.0.1
And if the Interface name is other than eth0 ( let’s assume em1 ) then go to
Virtualizor Admin panel -> Configuration -> Slave settings(choose server from dropdown to select a slave , if any) -> em1 -> save.
Then try to start virtnetwork service :
service virtnetwork start
If you have an existing bridge created on your server (possibly in Xen: xenbr1 ) then you need to mention it in Configuration->Slave settings-> Paravirtualization Bridge and HVM Bridge .
Else you may need to mention viifbr0 in that page.
In case of KVM, if you have an existing bridge br0, then you can set that bridge name in /usr/local/virtualizor/universal.php file.
$globals['bridge'] = 'br0';
If you want Virtnetwork to be a permanent bridge and not run as a service then you can follow this guide to create bridge :
Note: Restarting virtnetwork will require you to stop and start the existing vps on panel.