User manual PARALLELS VIRTUOZZO CONTAINERS FOR WINDOWS DATASHEET

[. . . ] Parallels Parallels Virtuozzo Containers for Windows User's Guide Version 4. 5 Copyright © 1999-2009 Parallels Holdings, Ltd. ISBN: N/A Parallels Holdings, Ltd. 13755 Sunrise Valley Drive Suite 600 Herndon, VA 20171 USA Tel: +1 (703) 815 5670 Fax: +1 (703) 815 5675 Copyright © 1999-2009 Parallels Holdings, Ltd. Parallels, Coherence, Parallels Transporter, Parallels Compressor, Parallels Desktop, and Parallels Explorer are registered trademarks of Parallels Software International, Inc. Virtuozzo, Plesk, HSPcomplete, and corresponding logos are trademarks of Parallels Holdings, Ltd. [. . . ] The first pool (Pool_1) will consist of two processors and the second one (Pool_2) will include the four remaining processors. To this effect, execute the following commands on the physical server: To make the first CPU pool: C:\. . . \Administrator>vzcpucfg pool set Pool_1 0-1 To make the second CPU pool: C:\. . . \Administrator>vzcpucfg pool set Pool_2 2-5 0-1 (the processors numeration starts from zero) and 2-5 in the commands above denote the index number of processors installed on the physical server. Index numbers can be specified as one CPU range (0-1) or several CPU ranges (0-1, 3, 4-5). In the latter case you should separate the indicated ranges by commas. Note: You can include one and the same processor in more than one CPU pool. For example, you can create Pool_3 and add the processors with index numbers 0, 1, 4, and 5 to it using the following command: vzcpucfg pool set Pool_3 0-1, 4-5 You can check that both pools have been successfully created using the following command: C:\. . . \Administrator>vzcpucfg pool list CPUPOOL AFFINITY default 0-5 Pool_1 0-1 Pool_2 2-5 Pool_3 0-1, 4-5 Now that you have created two additional pools, you can assign them to your Containers. Detailed information on how you can do it is given in the Assigning CPU Pools to Containers subsection (p. 166). Managing Resources 165 Configuring Pools Using the vzcpucfg utility, you can configure the number of processors constituting the corresponding CPU pool. If, for example, you have Pool_1 that contains two CPUs (0 and 1) and wish to add another CPU to this pool, you can execute the following command: C:\. . . \Administrator>vzcpucfg pool set Pool_1 0-2 You can also configure the number of processors in the default CPU pool which originally includes all the processors installed on the physical server. For example, if your server has 6 processors (0-5) installed, you can reduce the number of processors in the default pool by 2 CPUs as follows: C:\. . . \Administrator>vzcpucfg pool set default 0-3 To check the number of processors currently included in your CPU pools, use the following command: C:\. . . \Administrator>vzcpucfg pool list CPUPOOL AFFINITY default 0-3 Pool_1 0-2 Pool_2 2-5 As you can see, now the Pool_1 pool comprises three processors (0, 1, and 2) and the default pool contains only four processors (0, 1, 2, and 3). Deleting CPU Pools You can use the vzcpucfg command to delete any of the existing CPU pools, except for the default one. Assuming that you have three CPU pools on your physical server (default, Pool_1, and Pool_2), you can delete Pool_1 as follows: C:\. . . \Administrator>vzcpucfg pool del Pool_1 To check that the pool has been successfully deleted, run the following command: C:\. . . \Administrator>vzcpucfg pool list CPUPOOL AFFINITY default 0-5 Pool_2 2-5 As you can see from the command output, Pool_1 is not present any more in the list of existing CPU pools. If Pool_1 was assigned to some Containers, these Containers are automatically bound to the default CPU pool and start using the processors from this pool. When removing CPU pools from your Hardware Node, keep in mind the following: If you are migrating a Container associated with some CPU pool to a Hardware Node that does not have such a pool, the Container is assigned to the default CPU pool on this Node. If you are restoring a Container that was associated with some CPU pool at the time of its backing up on a Hardware Node that does not have such a pool, the restored Container is assigned to the default CPU pool on this Node. Managing Resources 166 Assigning CPU Pools to Containers All newly created Containers are set to consume the CPU time of the processors from the default CPU pool. However, if you have created one or more additional CPU pools, you can configure your Containers to make use of the processors included in these pools. Let us assume the following: Your physical server has six processors installed. Pool_1 includes two processors (0 and 1) and Pool_2 contains four processors (2-5). You wish the processes running inside Container 101 to be executed on the processors from Pool_1 and the processes running Container 102 on the processors from Pool_2. To do this, you should perform the following operations: 1 Assign Pool_1 to Container 101 and Pool_2 to Container 102 by executing the following commands: C:\. . . \Administrator>vzctl set 101 --cpupool Pool_1 --save C:\. . . \Administrator>vzctl set 102 --cpupool Pool_2 --save 2 Restart the Containers for the changes to take effect: C:\. . . \Administrator>vzctl restart 101 C:\. . . \Administrator>vzctl restart 102 To check that Container 101 and 102 are now bound to Pool_1 and Pool_2, respectively, run the following command: C:\. . . \Administrator>vzlist -o ctid, cpupool CTID CPUPOOL 101 Pool_1 102 Pool_2 Now imagine the following situation. For some reason, you need to remove the processor with index 1 from the physical server. This processor is included in Pool_1 which is, in its turn, assigned to Container 101. As soon as you remove the processor from the server, Container 101 will be automatically reassigned to the default pool. [. . . ] Host Operating System (or Host OS) is an operating system installed on the Hardware Node. MAC address stands for Media Access Control address, a hardware address that uniquely identifies each Node in a network. Consequently, each different type of network media requires a different MAC layer. OS template (or Operating System template) is used to create new Containers with a preinstalled operating system. [. . . ]