There are certain Xen related settings you would like to configure on your NODE.
You can change these settings any time from the Virtualizor Admin Panel -> Configuration -> Slave Settings.
The following is a screenshot of the available settings :
Xen Dom0 Memory
In Xen, the host node also known as Domain-0 (or Dom0) is allocated a fixed amount of ram so that the remaining RAM is available for VPS creation. e.g. If your Node has 32 GB Ram and you allocate 1GB Ram to Dom0 then 31GB Ram will be available for creating VMs. By default 768 MB ram is allocated to the Dom0 by Virtualizor.
You can specify the Xen Bridge created by Xen here. If you have eth1 or any other device as your Ethernet device other than eth0 than Xen will create xenbr1. In such a case you will need to enter the name of the bridge created by xen. This setting configures Virtualizor to use the xenbr1 bridge rather than the default xenbr0 for the Virtual Machines network to work correctly.
Note : If there are existing VMs on the Node, you will need to shutdown all VMs.
- Xen 4.1+ installed on a Xen Node
- Virtualizor 2.6.6+
Stop and Disable XM
You will need to stop and disable Xend to start. For this firstly make sure that all VMs have been shutdown :
root> xm list Name ID Mem VCPUs State Time(s) Domain-0 0 768 4 r----- 39241.8
Only Domain-0 should be there in this list.
Now lets stop the Xend service :
root> service xend stop
Then prevent / disable it to start the next time.
root> chkconfig xend off
Enable XL in Virtualizor
You will now need to enable XL in Virtualizor for this Node.
To do so please login to the Virtualizor Admin Panel -> Configuration -> Slave Settings
Set the active server accordingly. Then scroll down and check the setting “Use XL”.
Note : You will require to add PV and HVM bridge in the below setting page in order to use XL.
Virtualizor default bridge is viifbr0 for PV and HVM.
Edit Existing VMs
If there are existing VMs, you will need to edit them in Virtualizor so that the new configuration is set.
That’s it you are all set. Now start the VMs using Virtualizor.