[PDF] Parallels Server 5 Bare Metal

More documents

Recommendations

Info

Managing Resources This output shows that the MyVM virtual machine has the unique identifier of 5c1fb1bb-4364-4b42- 86b2-c584bdd2223b and the kernel virtual machine ID of 2075205468. Notes: For more information on pstat and its options, see the Parallels Server 5 Bare Metal Reference Guide. Managing Memory Parameters for Containers This section describes the VSwap memory management system introduced in Parallels Server 5 Bare Metal. You will learn to do the following: • Configure the main VSwap parameters for Containers (p. 141). • Set the memory allocation limit in Containers (p. 142). • Enhance the VSwap functionality (p. 143). If you have upgraded to Parallels Server 5 Bare Metal, you will also learn how the system calculates the new VSwap values (p. 144) from the memory parameters that were applied to Containers before the upgrade. 140
Configuring Main VSwap Parameters Managing Resources Parallels Server 5 Bare Metal introduces a new scheme for managing memory-related parameters in Containers—VSwap. Like many other memory management schemes used on standalone Linux computers, this scheme is based on two main parameters: • RAM. This parameter determines the total size of RAM that can be used by the processes of a Container. • swap. This parameter determines the total size of swap that can be used by the Container for swapping out memory once the RAM is exceeded. Notes: 1. In Parallels Server 5 Bare Metal, the new VSwap memory management scheme has replaced the SLM scheme. 2. You can also set memory limits for and provide memory guarantees to Containers by configuring multiple UBC (User Beancounter) parameters (numproc, numtcpsock, vmguarpages, and so on). These parameters provide you with comprehensive facilities of customizing the memory resources in respect of your Containers. However, this way of managing system resources is more complex and requires more effort to be made on your part to adopt it to your system. For detailed information on UBC parameters, refer to the Administrator's Guide to Managing UBC Resources available at http://www.parallels.com/products/pvcl/resources/docs. The new memory management scheme works as follows: 1 You set for a Container a certain amount of RAM and swap space that can be used by the processes running in the Container. 2 When the Container exceeds the RAM limit set for it, the swapping process starts. The swapping process for Containers slightly differs from that on a standalone computer. The Container swap file is virtual and, if possible, resides in the Node RAM. In other words, when the swap-out for a Container starts and the Node has enough RAM to keep the swap file, the swap file is stored in the Node RAM rather than on the hard drive. 3 Once the Container exceeds its swap limit, the system invokes the OOM Killer for this Container. 4 The OOM Killer chooses one or more processes running in the affected Container and forcibly kills them. By default, any newly created Container starts using the new memory management scheme. To find out the amount of RAM and swap space set for a Container, you can check the values of the PHYSPAGES and SWAPPAGES parameters in the Container configuration file, for example: # grep PHYSPAGES /etc/vz/conf/101.conf PHYSPAGES="65536:65536" # grep SWAPPAGES /etc/vz/conf/101.conf SWAPPAGES="65536" 141
Page 1 and 2:
Parallels Server 5 Bare Metal User'
Page 3 and 4:
Contents Introduction .............
Page 5 and 6:
Contents Making Screenshots .......
Page 7 and 8:
Contents Setting Up Private Network
Page 9 and 10:
C HAPTER 1 Introduction This chapte
Page 11 and 12:
Documentation Conventions Introduct
Page 13 and 14:
Feedback Introduction If you spot a
Page 15 and 16:
Learning Parallels Server 5 Bare Me
Page 17 and 18:
Basics of OS Virtualization Learnin
Page 19 and 20:
Parallels Server Bare Metal Configu
Page 21 and 22:
Parallels Virtual Machines Learning
Page 23 and 24:
Virtual Machine Files Learning Para
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Managing Virtual Machines and Conta
Page 31 and 32:
Supported Guest Operating Systems M
Page 33 and 34:
Choosing a Container ID Managing Vi
Page 35 and 36:
Configuring Network Settings Managi
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Configuring the Default Directories
Page 43:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91: Managing Virtual Machines and Conta
Page 110 and 111: C HAPTER 4 Managing Resources The m
Page 112 and 113: Managing Resources Managing CPU Sha
Page 114 and 115: Managing Resources Configuring the
Page 116 and 117: Managing Resources Configuring CPU
Page 118 and 119: Managing Resources Turning On and O
Page 122 and 123: Managing Resources Checking Quota S
Page 124 and 125: Managing Resources Moving Container
Page 126 and 127: Managing Resources Detaching Contai
Page 128 and 129: Managing Resources Configuring Netw
Page 130 and 131: Managing Resources Viewing Network
Page 134 and 135: Managing Resources Configuring Netw
Page 136 and 137: Managing Resources Configuring Prio
Page 138 and 139: Managing Resources Saved parameters
Page 142 and 143: Managing Resources In this example,
Page 144 and 145: Managing Resources Configuring Lega
Page 146 and 147: Managing Resources Configuring Addi
Page 148 and 149: Managing Resources To revert to the
Page 150 and 151: Managing Resources Managing Contain
Page 152 and 153: Managing Resources Scaling Containe
Page 154 and 155: Managing Resources Applying New Con
Page 156 and 157: Managing Services and Processes Wha
Page 158 and 159: Managing Services and Processes Man
Page 160 and 161: Managing Services and Processes The
Page 162 and 163: Managing Services and Processes Cha
Page 164 and 165: C HAPTER 6 Managing Parallels Serve
Page 166 and 167: Managing Parallels Server Bare Meta
Page 190 and 191:
Managing Parallels Server Bare Meta
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Managing Licenses Installing the Li
Page 198 and 199:
Managing Licenses Transferring the
Page 200 and 201:
Managing Licenses Viewing the Licen
Page 202 and 203:
Managing Licenses 202 key_number="P
Page 204 and 205:
Keeping Your System Up To Date Upda
Page 206 and 207:
Keeping Your System Up To Date 206
Page 208 and 209:
Page 210 and 211:
Keeping Your System Up To Date 210
Page 212 and 213:
Page 214 and 215:
Page 216 and 217:
Advanced Tasks Creating VZFS Symlin
Page 218 and 219:
Advanced Tasks Capabilities Defined
Page 220 and 221:
Advanced Tasks Creating Customized
Page 222 and 223:
Advanced Tasks # vzmktmpl /root/cen
Page 224 and 225:
Advanced Tasks 224 • %packages: a
Page 226 and 227:
Advanced Tasks # rpm -ihv /root/mys
Page 228 and 229:
Advanced Tasks Obtaining Server ID
Page 230 and 231:
Advanced Tasks Setting Immutable an
Page 232 and 233:
Advanced Tasks LowTotal: 8000 kB Lo
Page 234 and 235:
Advanced Tasks Loading iptables Mod
Page 236 and 237:
Advanced Tasks Creating Configurati
Page 238 and 239:
Advanced Tasks %KM Kernel memory us
Page 240 and 241:
Advanced Tasks Checking partition a
Page 242 and 243:
Advanced Tasks The number of cylind
Page 244 and 245:
Advanced Tasks Running Parallels Se
Page 246 and 247:
C HAPTER 10 Troubleshooting This ch
Page 248 and 249:
Troubleshooting (The 65531 ports sc
Page 250 and 251:
Troubleshooting Saving Kernel Fault
Page 252 and 253:
Troubleshooting Failure to Start a
Page 254 and 255:
Troubleshooting Getting Technical S
Page 256 and 257:
Troubleshooting In this window, you
Page 258 and 259:
Troubleshooting Establishing Secure
Page 260 and 261:
C HAPTER 11 Glossary This glossary
Page 262 and 263:
Index Index A About This Guide - 9
Page 264 and 265:
Index Managing Memory Resources for
show all

[PDF] Parallels Server 5 Bare Metal

Create successful ePaper yourself

Delete template?

Save as template?