- Timestamp:
- Sep 16, 2013 11:55:45 AM (12 years ago)
- svn:sync-xref-src-repo-rev:
- 88975
- Location:
- trunk/doc/manual
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/manual/en_US/user_AdvancedTopics.xml
r48257 r48485 1165 1165 200 seconds to detect this situation. The VM will fail to power 1166 1166 up.</para> 1167 </sect2>1168 </sect1>1169 1170 <sect1>1171 <title>Launching more than 128 VMs on Linux hosts</title>1172 1173 <para>Linux hosts have a fixed number of IPC semaphores IDs per process1174 preventing users from starting substantially many VMs. The exact number1175 may vary with each Linux distribution. While trying to launch more VMs you1176 would be shown a "Cannot create IPC semaphore" error. In order to run more1177 VMs, you will need to increase the semaphore ID limit of the VBoxSVC1178 process. Find the current semaphore limits imposed by the kernel by1179 executing as root:<screen>#/sbin/sysctl kernel.sem1180 kernel.sem = 250 32000 32 128</screen></para>1181 1182 <para>The "kernel.sem" parameter bundles together 4 values, the one we are1183 interested in is called "SEMMNI", the maximum number of semaphore IDs1184 which is 128 in the above example. Increase this semaphore ID limit by1185 executing as root:<screen>echo "kernel.sem = 250 32000 32 2048" >> /etc/sysctl.conf1186 /sbin/sysctl -p</screen></para>1187 1188 <para>The above commands will add the new limits to the configuration file, thus1189 making the effect persistent across reboots, and will activate the new1190 limits into the currently running kernel.</para>1191 </sect1>1192 1193 <sect1>1194 <title>Launching more than 120 VMs on Solaris hosts</title>1195 1196 <para>Solaris hosts have a fixed number of IPC semaphores IDs per process1197 preventing users from starting more than 120 VMs. While trying to launch1198 more VMs you would be shown a "Cannot create IPC semaphore" error. In1199 order to run more VMs, you will need to increase the semaphore ID limit of1200 the VBoxSVC process.</para>1201 1202 <sect2>1203 <title>Temporary solution while VirtualBox is running</title>1204 1205 <para>Execute as root the <computeroutput>prctl</computeroutput> command1206 as shown below for the currently running VBoxSVC process. The process ID1207 of VBoxSVC can be obtained using the <computeroutput>ps</computeroutput>1208 command.</para>1209 1210 <screen>prctl -r -n project.max-sem-ids -v 2048 <pid-of-VBoxSVC></screen>1211 1212 <para>This will immediately increase the semaphore limit of the1213 currently running VBoxSVC process and allow you to launch more VMs.1214 However, this change is not persistent and will be lost when VBoxSVC1215 terminates.</para>1216 </sect2>1217 1218 <sect2>1219 <title>Persistent solution, requires user to re-login</title>1220 1221 <para>If the user running VirtualBox is root, execute the following1222 command:</para>1223 1224 <screen>prctl -n project.max-sem-ids -v 2048 -r -i project user.root</screen>1225 1226 <para>From this point, starting new processes will have the increased1227 limit of 2048. You may then re-login or close all VMs and restart1228 VBoxSVC. You can check the current VBoxSVC semaphore ID limit using the1229 following command:</para>1230 1231 <screen>prctl -n project.max-sem-ids -i process <pid-of-VBoxSVC></screen>1232 1233 <para>If the user running VirtualBox is not root, you must add the1234 property to the user's default project. Create the default project and1235 set the limit by executing as root:</para>1236 1237 <screen>projadd -U <username> user.<username>1238 projmod -s -K "project.max-sem-ids=(priv,2048,deny)" user.<username></screen>1239 1240 <para>Substitute "<username>" with the name of the user running1241 VirtualBox. Then re-login as this user to be able to run more than 1201242 VMs.</para>1243 1167 </sect2> 1244 1168 </sect1> -
trunk/doc/manual/user_ChangeLogImpl.xml
r48359 r48485 137 137 <para>Main: new event queue implementation which does not use the host's 138 138 native event queue for processing VirtualBox events anymore</para> 139 </listitem> 140 141 <listitem> 142 <para>Main: eliminate the use of SysV semaphores on all host OSes 143 other than Windows, namely Linux, Solaris and Mac OS X, with the 144 consequence that no system reconfiguration is needed to run more 145 than approximately 100 VMs</para> 139 146 </listitem> 140 147
Note:
See TracChangeset
for help on using the changeset viewer.