After I setup a Virtualizor slave server and connected it to a Virtualizor master server, the virtnetwork service would not start on the slave server. After reviewing the network configuration for Virtualizor, it appears that the slave server inherited the name of the network interface from the master server, which was different than the name of the network interface on the slave server. After manually updating the network interface name on the slave server, virtnetwork started properly and the Virtualizor master server was able to communicate with the slave server.
Replicating this issue should only require adding a slave server to a master server and then checking the "Network Interface" option under the "Network Settings" area of the slave server's settings. The slave server and master server should have different names for their network interfaces.