VirtualBox

Changeset 38967 in vbox


Ignore:
Timestamp:
Oct 7, 2011 6:32:06 PM (13 years ago)
Author:
vboxsync
Message:

doc/manual: Document persistent max-sem-ids limit bumping for Solaris hosts.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/doc/manual/en_US/user_AdvancedTopics.xml

    r38574 r38967  
    10451045    <para>Solaris hosts have a fixed number of IPC semaphores IDs per process
    10461046    preventing users from starting more than 120 VMs. While trying to launch
    1047     more VMs you would be shown a "Cannot create IPC semaphore" error.</para>
    1048 
    1049     <para>In order to run more VMs, you will need to bump the semaphore ID
    1050     limit of the VBoxSVC process. Execute as root the
    1051     <computeroutput>prctl</computeroutput> command as shown below. The process
    1052     ID of VBoxSVC can be obtained using the
    1053     <computeroutput>ps</computeroutput> list command.</para>
    1054 
    1055     <para><screen>prctl -r -n project.max-sem-ids -v 2048 &lt;pid-of-VBoxSVC&gt;</screen></para>
     1047    more VMs you would be shown a "Cannot create IPC semaphore" error. In
     1048    order to run more VMs, you will need to increase the semaphore ID limit of
     1049    the VBoxSVC process.</para>
     1050
     1051    <sect2>
     1052      <title>Temporary solution while VirtualBox is running</title>
     1053
     1054      <para>Execute as root the <computeroutput>prctl</computeroutput> command
     1055      as shown below for the currently running VBoxSVC process. The process ID
     1056      of VBoxSVC can be obtained using the <computeroutput>ps</computeroutput>
     1057      command.</para>
     1058
     1059      <screen>prctl -r -n project.max-sem-ids -v 2048 &lt;pid-of-VBoxSVC&gt;</screen>
     1060
     1061      <para>This will immediately increase the semaphore limit of the
     1062      currently running VBoxSVC process and allow you to launch more VMs.
     1063      However, this change is not persistent and will be lost when VBoxSVC
     1064      terminates.</para>
     1065    </sect2>
     1066
     1067    <sect2>
     1068      <title>Persistent solution, requires user to re-login</title>
     1069
     1070      <para>If the user is running VirtualBox is root, execute the following
     1071      command:</para>
     1072
     1073      <screen>prctl -n project.max-sem-ids -v 2048 -r -i project user.root</screen>
     1074
     1075      <para>From this point, starting new processes will have the increased
     1076      limit of 2048. You may then re-login or close all VMs and restart
     1077      VBoxSVC. You can check the current VBoxSVC semaphore ID limit using the
     1078      following command:</para>
     1079
     1080      <screen>prctl -n project.max-sem-ids -i process &lt;pid-of-VBoxSVC&gt;</screen>
     1081
     1082      <para>If the user running VirtualBox is not root, you must add the
     1083      property to the user's default project. Create the default project and
     1084      set the limit by executing as root:</para>
     1085
     1086      <screen>projadd -U &lt;username&gt; user.&lt;username&gt;
     1087projmod -s -K "project.max-sem-ids=(priv,2048,deny)" user.&lt;username&gt;</screen>
     1088
     1089      <para>Substitute "&lt;username&gt;" with the name of the user running
     1090      VirtualBox. Then re-login as this user to be able to run more than 120
     1091      VMs.</para>
     1092    </sect2>
    10561093  </sect1>
    10571094
Note: See TracChangeset for help on using the changeset viewer.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette