Installing Softaculous Virtualizor for XenServer is very simple.
- XenServer 6.2 or XenServer 6.5 or XenServer 7.1 or XenServer 7.2 or XenServer 7.3 or XenServer 7.4 or XenServer 7.5 or XenServer 7.6 or XenServer 8
- XenServer 6.2 or XenServer 6.5 or XenServer 7.1 or XenServer 7.2 needs to be installed before and Virtualizor will be installed on that.
- Before installing virtualizor on Xenserver 6.5 you will require to disable cirtix repo to start virtualizor installation.
You can disable repo(For Xenserver 6.5 only) with following command from "CLI":
sed -i 's/^enabled=1/enabled=0/' /etc/yum.repos.d/Citrix.repo
- After installation of virtualizor is completed you can enable it.
You can enable repo(For Xenserver 6.5 only) with following command from "CLI":
sed -i 's/^enabled=0/enabled=1/' /etc/yum.repos.d/Citrix.repo
- Before installing virtualizor on Xenserver 7.1 you will require to enable Centos-Base repo to start virtualizor installation.
You can enable repo(For Xenserver 7.1 and above only) with following command from "CLI":
sed -i 's/^enabled=0/enabled=1/' /etc/yum.repos.d/CentOS-Base.repo
- After installation of virtualizor is completed you can disable it.
You can disable repo(For Xenserver 7.1 and above only) with following command from "CLI":
sed -i 's/^enabled=1/enabled=0/' /etc/yum.repos.d/CentOS-Base.repo
XenServer does not allow you to change the partition scheme much. When XenServer is installed it will be installed with 4GB space for the OS and the remaining will be assigned to a LVM Volume Group. Virtualizor will use the Volume Group for the VMs being created. You will land up with the following Partition scheme in XenServer :
|/||4 GB|| Root partition containing all Hardware |
Node operating system files
|SWAP||512MB +|| Paging partition for the Linux operating |
|LVG (Volume Group)||All the remaining space on the hard disk|| This partition will be used to create Logicall Volumes |
that will act as the VPS (DomUs) storage.
NOTE : You must NOT create any Logical Volume and
MOUNT it. This must be an EMPTY VOLUME
Virtualizor will not delete any pre-existing
LVs in theVolume Group.
But its recommended to have an empty
( LVM | File | Thin LVM | ZFS | ZFS Thin | ZFS Compressed | ZFS Thin Compressed )
Open a Shell Terminal (e.g. PuTTY) and SSH to your server. Run the following commands:
wget -N http://files.virtualizor.com/install.sh
chmod 0755 install.sh
./install.sh email@example.com kernel=xcp lvg=VOLUME_GROUP_NAME repo_size=SIZE
Please give the email address correctly !
- email - The Admin Email Address
- kernel - In this case its xcp
- lvg - The Volume Group that will be used for the DomU (VPS) storage e.g. defaults to vg. It should have some OR ALL unallocated space to create LVMs for the VPS.
- repo_size - The size of the Template Repository in GB (Should be numeric only). Where all the Templates are stored. (Recommended size is 100).
- Optional options
virtmedia_VG - If you have more then two repository, you can use either repository to be used for the virtualizor media.
noos - If you don't want to download the DomU operating system i.e. OS Templates, then please add noos=true as a parameter
beta - If there is a newer version of Virtualizor available and you would like to test it then please add beta=true as a parameter
- license - In case you are installing Virtualizor on internal network you will need to provide the VALID license key. To get internal license key you will need to open a support ticket.
The installation will begin immediately. It may seem that the installation has stopped, if your network speed is slow, but please let it continue. You will see something like this :
After the installation is completed you will be asked to reboot.
You can then visit the Admin Panel to create Virtual Servers and also manage your server.
Note : A log file of the installation process will be created - /root/virtualizor.log
To login to the Softaculous Virtualizor Admin Panel, visit the following URL :
Login with the servers root details.
After you login, you will see the Admin Panel Dashboard :
Virtualizor uses ports from 4081 - 4085. If there is any firewall restricting this, you will need to allow these ports.
For RHEL & CentOS < 7
iptables -I INPUT 1 -p tcp -m tcp --dport 4081:4085 -j ACCEPT
iptables -I INPUT 2 -p tcp -m tcp --dport 5900:6000 -j ACCEPT
For RHEL & CentOS 7+
firewall-cmd --zone=public --permanent --add-port=4081-4085/tcp
firewall-cmd --zone=public --permanent --add-port=5900-6000/tcp