Virtualizor XenServer

Virtualizor XenServer

gauthig	April 19, 2015, 2:20 am \| Post: 1
Group: Member Post Group: Newbie Posts: 12 Status:	I also need xenserver support. For what I have tested so far is that virtualizor does not understand the xenpool, I used a virtualizor master and slaved each xenserver after installing virtualizor on them also, i.e. virtualizor needs to be the master and have each node under it's control, not xenserver pool. But here are some issues I still have and am waiting for others to respond if they know how to fix these: 1. When creating an active/active bond out of two of the NIC's and creating a public network, virtualizor keeps trying to setup the network to the bond and not the network defined as default. This causes the following error -Start - Host cannot attach network (in the case of NIC bonding, this may be because attaching the network on this host would require other networks [that are currently active] to be taken down).This is a known xenserver error where you must select the public network. There seems to be no setting in virtualizor to use the correct public network which is set as the default. It always uses "Network 0" which is the bond. 2. Each creation of a new VPS seems to go to only the first attached xenserver, it does not round robin or look at any load balancing. It would be great to have it just round robin and create a new VPS in a different slave xenserver. That feature does seem to work if you use openvz.
IP: --

Users viewing this topic
	1 guests, 0 users.