A brief Virtuozzo beginners walkthrough

1) We will login to the portal and view our Hardware information.

a. manage

b.hardware

c.Locate your server and click ‘view’.

Portal Information
d. Note the Public IP and Password.

2)Browse to the Public IP of the server in your preferred browser, using HTTPS.  It is advised to use Firefox, Opera, or Internet Explorer for managing Virtuozzo via the PIM.  JavaScript is REQUIRED.  Without JavaScript you may be redirected to a non-existent page and the PIM will simply not work.

3) Enter the Username and Password to login to the PIM.  Remember, unlike Plesk the username is ‘root’ and the password is the root password to the server, as listed in the Portal.

PIM Login Screen

4) Now you will need to decide which templates you need, install them and have them cached.

a.Management

b.Updates

c.Go to the server you wish to update.

d.Go to Template Updates


e.Select any additional templates you wish to install or update.

5)  Go to the Server you wish to update, under Infrastructure on the left.

a. Go to Templates

b. Go to OS Templates

c. Select the OS Templates you wish to utilize on the server and cache.  Note that you will not typically need to cache all of the Templates to start with.  Only cache the Templates you wish to use.  These will take up a significant amount of space in your /vz partition.

d. If you only have one node at this time then click the next cache button.

e.  You will now need to wait for the full template rpm’s to be downloaded and installed.

f. You can click the “Details” link to view the status of the caching.

6)   While the server is downloading and caching the templates we can setup our network range to be used by our Containers.  Go to Setup and Network.

a. Click New IP Range

b.  Add your additional IP addresses to be used by your Containers here.  If you have not yet purchased additional IP addresses for your virtual servers then you will need to do this now via ‘manage –> public network –> ip manager –> order more ip addresses –> static –> select this server – route your new subnet to this ip address’

6    Now go back to your hardware node, under Infrastructure, into Containers and New Container.

a. Fill out the information as to how it best suites your needs.  For this example we are using slm.512MB as the defaults – this will be reviewed in an upcoming step.

b.  Fill out the hostname as a Fully Qualified Domain Name, add your DNS Server (See this article) and add a search domain if needed(this is not typically needed)

c. Review the resource parameters.  Be very careful in this stage as you can drastically hinder the Containers ability to process data, disk space, memory or even give too much which will starve your server of resources causing it to go slow or even kill processes unexpectedly.  If you do not understand these settings then it is advised to contact your server administrator or a 3rd party management company.  You will want to click ‘Validate’ prior to clicking ‘Next’ to insure that your settings do not conflict with each other.

d.  Select the applications you wish to install and click Next

e. Review your configuration and Create


f.  You have completed the creation of a Container.


g.  You can now go back to Containers to view the new Container and obtain the automatically assigned IP address(from the pool of IP’s you added earlier)

h.  You are now ready to login to your server and begin using it.


myname/myserver[0]~$ ssh 1.234.123.4
Warning: Permanently added '1.234.123.4' (DSA) to the list of known hosts.
root@1.234.123.4's password:
[root@test01 ~]# ip a s
1: lo: mtu 16436 qdisc noqueue
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
3: venet0: mtu 1500 qdisc noqueue
    link/void
    inet 127.0.0.1/32 scope host venet0
    inet 1.234.123.4/32 brd 1.234.123.4 scope global venet0:0
[root@test01 ~]# ps auxww
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         1  0.0  0.1  10328   744 ?        Ss   13:23   0:00 init [3]
root     20419  0.0  0.1  12580   632 ?        Sroot     21726  0.0  0.2  60532  1220 ?        Ss   13:23   0:00 /usr/sbin/sshd
root     21737  0.0  0.1  22512   892 ?        Ss   13:23   0:00 xinetd -stayalive -pidfile /var/run/xinetd.pid
root     21756  0.0  0.3  62732  2052 ?        Ss   13:23   0:00 sendmail: accepting connections
smmsp    21764  0.0  0.3  57608  1752 ?        Ss   13:23   0:00 sendmail: Queue runner@01:00:00 for /var/spool/clientmqueue
root     21776  0.0  2.0 283796 10728 ?        Ss   13:23   0:00 /usr/sbin/httpd
root     21786  0.0  0.2  20832  1144 ?        Ss   13:23   0:00 crond
root     21796  0.0  0.1  46648   800 ?        Ss   13:23   0:00 /usr/sbin/saslauthd -m /var/run/saslauthd -a pam -n 2
apache   21797  0.0  1.1 283932  5788 ?        S    13:23   0:00 /usr/sbin/httpd
root     21798  0.0  0.1  46648   544 ?        S    13:23   0:00 /usr/sbin/saslauthd -m /var/run/saslauthd -a pam -n 2
root     23573  0.0  0.6  85876  3240 ?        Rs   13:45   0:00 sshd: root@pts/0
root     23594  0.0  0.3  12044  1604 pts/0    Ss   13:45   0:00 -bash
root     23626  0.0  0.1  10700   952 pts/0    R+   13:45   0:00 ps auxww

[root@test01 ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
vzfs                  1.0G   64M  961M   7% /
none                 1004M  4.0K 1004M   1% /dev
[root@test01 ~]#