Virtualizor Network Failure after Reboot

When Virtualizor experiences a reboot, it will sometime fail to bring the virtual network back online, which causes cascading issues with internal DHCP server requests from the VMs and the hypervisor.

1. Restart virtnetwork service to bring back online the virtual network bridge

   1. service virtnetwork restart

2. Restart dhcpd service to make the DHCP server aware of the settings reinitialized by the virtual network

   1. service dhcpd restart

3. Check multiple VMs to ensure they are able to reach the internet and external connections can be made to them (ie. RDP and/or PING, note Windows Server by default typically disables ICMP PING requests.)