Getting started with OpenVZ live CD - Revision history

Kir: categorized

2007-12-11T13:16:37Z

categorized

2007-07-22T03:35:25Z

‎Setting up VE networking

2007-07-06T07:12:05Z

moved information about shmpages to appropriate place

2007-07-06T06:50:52Z

‎VE creation: centos case added

2007-07-04T13:42:56Z

remove knoppix mentioning: we have now one more LiveCD based on Centos 4.4

2007-06-10T16:51:56Z

2007-05-27T21:55:54Z

‎Starting VE

2007-05-27T21:54:20Z

‎Links: spelling ==db

2007-05-27T21:51:05Z

‎Executing commands in VE

2007-05-27T21:50:18Z

‎Executing commands in VE: Explained diff btwn nproc and # of cpu's ==db

← Older revision		Revision as of 13:16, 11 December 2007
Line 257:		Line 257:

	If you experience some difficulties, contact us via http://forum.openvz.org/ . Templates and other tools are available from http://download.openvz.org/ .		If you experience some difficulties, contact us via http://forum.openvz.org/ . Templates and other tools are available from http://download.openvz.org/ .
		+
		+	[[Category: Live CD]]

@@ Line 127: / Line 127: @@
 </pre>
-However, it is not possible to ping other computers in the network: for it we need tot
+However, it is not possible to ping other computers in the network: for it we need to
 set up NAT (Network Address Translation) and set the nameserver.

@@ Line 46: / Line 46: @@
        VEID      NPROC STATUS  IP_ADDR         HOSTNAME
           5 running                 -
 </pre>
@@ Line 141: / Line 127: @@
 </pre>
-However, it is not possible to ping other computers in the network: for it we need to
+However, it is not possible to ping other computers in the network: for it we need tot
 set up NAT (Network Address Translation) and set the nameserver.
@@ Line 209: / Line 195: @@
+#
 </pre>
 == Resource limiting ==
 The very important feature of VE is that you can limit it by resources: CPU, memory, disk space.
-It is also performed via vzctl. Current usage values and limits of memory-related resources can be viewed through
+It is also performed via vzctl. For example to set '''shmpages''' (shared memory pages) barrier:limit you
 <code>/proc/bc/VEID/resources</code> file:
 <pre>
-# cat /proc/bc/101/resources
+# cat /proc/bc/101/resources # or /proc/user_beancounters on 2.6.9 kernels
              kmemsize         628209     976969    2752512    2936012          0
              lockedpages           0          0         32         32          0

@@ Line 16: / Line 16: @@
 </pre>
-'''vzctl''' is the tool that manages VEs. Look in <tt>/var/lib/vz/template/cache/</tt> directory for other OS templates available on LiveCD:
+'''vzctl''' is the tool that manages VEs. Look in <tt>/vz/template/cache/</tt> (CentOS LiveCD)
 <pre>
 # ls -1 /var/lib/vz/template/cache/

@@ Line 1: / Line 1: @@
-This article is written for OpenVZ LiveCD and assumes that the reader only starts using OpenVZ.
+This article is written for OpenVZ LiveCD and assumes that the reader only starts using OpenVZ. ([[Download live CD]])
 == Introduction ==
 So, as you probably know, OpenVZ allows the user to create [[VE]]s, or Virtual Environments, which seem very much
 like real computers. Real computer can run various distributions: Debian, Gentoo, Red Hat and  Novell products, etc.
-In the same way, a VE can be based on various [[OS template|OS (Operating System) templates]]. On the LiveCD only few minimal OS templates are installed because of disk space limit. Each VE is indentified by its number -- a '''VEID'''.
+In the same way, a VE can be based on various [[OS template|OS (Operating System) templates]]. On the LiveCD only few minimal OS templates are installed because of disk space limit. Each VE is identified by its number -- a '''VEID'''.
 == VE creation ==

@@ Line 55: / Line 55: @@
 o This will give VE 101 64MB of shmpages; you may wish to give it more if you're planning on doing more than just basic openvz testing.
-o You can verify the change in-VE by issuing:
+o You can verify the change from the host by issuing:
 <pre>

@@ Line 258: / Line 258: @@
 == Links ==
-That's all you need to start playing with OpenVZ. Additional information can be found in man page on vzctl and at http://wiki.openvz.org/.
+That's all you need to start playing with OpenVZ. Additional information can be found in man page on vzctl and at http://wiki.openvz.org/ .
-If you expirience some difficulties, contact us via http://forum.openvz.org/. Templates and other tools are available from http://download.openvz.org/.
+If you experience some difficulties, contact us via http://forum.openvz.org/ . Templates and other tools are available from http://download.openvz.org/ .

@@ Line 62: / Line 62: @@
 == Executing commands in VE ==
-From the previous command you see that 5 processes are running inside VE 101. (The "NPROC" field indicates the number of Processes, or PIDs, that are active in the VE -- not the number of Processors, or CPUs.)  Being on usual [[hardware node]] you can use <code>ps</code> command to identify those, and the same command can be used here. The only difference is that this command should be called inside VE.
+From the "vzlist" command you see that 5 processes are running inside VE 101. (The "NPROC" field indicates the number of Processes, or PIDs, that are active in the VE -- not the number of Processors, or CPUs.)  Being on usual [[hardware node]] you can use <code>ps</code> command to identify those, and the same command can be used here. The only difference is that this command should be called inside VE.
 In order to perform any command inside VE `vzctl exec` is used: