Personal tools

HyperVM Installation Guide

From LxCenter Wiki

Jump to: navigation, search

Hypervm Installing Guide


  • A dedicated CentOS or Red Hat EL 5.x. CentOS 6.x is not currently supported by latest stable.
    1. For openvz
      • IBM PC-compatible computer;
      • Intel Celeron, Pentium II, Pentium III, Pentium 4, Xeon, or AMD Athlon CPU;
      • At least 128 MB of RAM;
      • Hard drive(s) with at least 4 GB of free disk space;
      • Network card (either Intel EtherExpress100 (i82557-, i82558- or i82559-based) or 3Com (3c905 or 3c905B or 3c595) or TL8139-based are recommended).
    2. For xen
      • One or more 64-bit x86 CPU(s), 1.5 GHz minimum, 2 GHz or faster multicore CPU recommended
      • RAM 1 GB minimum, 2 GB or more recommended
      • Disk Locally attached storage (PATA, SATA, SCSI) with 16 GB of disk space minimum, 60 GB of disk space recommended

Before we begin...

Important: Make sure that you open the ports 8888 and 8887 in the firewall. Otherwise you won’t be able to connect to HyperVM.

You have to disable selinux by editing /etc/sysconfig/selinux and changing the line to selinux=disabled and then running

# setenforce 0

You need to be at the latest release of your OS.

# yum update -y

Installing HyperVM

HyperVM installation consists of downloading either the or from and execute it as root. It will download all the required files and do the complete installation on it’s own.


# setenforce 0
# wget
# sh ./ --virtualization-type=xen/openvz/NONE

You have to explicitly specify which virtualization type you want using the option --virtualization-type as either:

  • xen
  • openvz
  • NONE

If you want to install hypervm on an existing system, just use virtualization-type=NONE, which will install just hyperVM components, and skip the virtualization components entirely.

HyperVM will currently install the openVZ/Xen kernel, but will not switch the default kernel to it. You will have to manually edit the /etc/grub.conf, and change the default=1 to default=0, and reboot the machine.


If you cannot connect to you HyperVM Control Panel, please check if HyperVM is running and your server firewall is not blocking access to ports 8888/tcp and 8887/tcp. You may temporarily disable it by running /etc/init.d/iptables stop

If you still cannot access your panel, go to our forums at and request help (you may want attach the file /root/hypervm-install/hypervm-linux/hypervm_install.log for easier troubleshooting).

Final Considerations

  • HyperVM supports the concept of multiple locations, and thus generally the question of harddisk partitioning is irrelevant. It is recommended to have a large / for openvz, since both /home and /vz will have files. You can just add another harddisk, mount it as a particular directory, and then add it to the list of locations. In other words, you can trivially distribute vpses across different harddisks/lvms. Also you can change the location of a vps from one harddisk to other from the CP itself. Go to vps home -> advanced -> change location.
  • You should never run any other control panel other than hyperVM on the host server. That will unncessarily introduce security risks, and in the case of openvz, since all the vps process are visible and accessible on the host server, starting and stopping of services on the host server will affect all the vpses too. If you need to run anything, create a special vps for it.
  • Once the machine boots back, just make sure you have the openVZ kernel by doing a ‘uname -a’, and after that you can connect to ‘http://machine-name:8888′ (8887 for https), and you will be presented with a login screen – The username will be admin and the password would be admin. Once you login, HyperVM will explicitly force you to change the password to something other.
  • For those installing Xen, please read through the Forum, and make sure that you meet all the requirements.
  • If you want to have a cluster, you have to run ‘’ in all the servers that you intend to make as slaves. Once ‘’ is completed, you can add the server from the ‘add server’ page in the master’s server page.
  • You will need to open port 8889 which is what’s used for communication between the master and slave. For file transfer, the slave will need to contact the master’s 8889 port, so you will need 8889 open on both master and the slave. All communication is fully encrypted and secure.
  • From then on, you can manage every aspect of Virtualization through our intuitive graphical interface.