virtualbox.org

Hi everyone,

After one week of troubleshooting, I decided to submit my Issue.
I have VirtualBox Version 5.1.10 installed on MacOS Sierra 10.12.1.
I have an Ubuntu 15.04 VM and when trying to install Oracle 11g on it, I have "parameter.semmni failed Expected Value 128".
I setup on ubuntu using sysctl the correct configuration.see below :

fs.suid_dumpable = 1
fs.aio-max-nr = 1048576
fs.file-max = 6815744
kernel.shmall = 2097152
kernel.shmmax = 536870912
kernel.shmmni = 4096
kernel.sem = 250 32000 100 128
net.ipv4.ip_local_port_range = 9000 65500
net.core.rmem_default = 4194304
net.core.rmem_max = 4194304
net.core.wmem_default = 262144
net.core.wmem_max = 1048586

My last hypothesis is that the MAC OS kerndrv has an issue to give access to kernel parameters.
on the MAC OS , :

• I uninstalled the VBOX and reinstalled it also setup
  I Installed VBox Extension Pack-5.1.10
  Reload VirtualBox
  Setup the Sysctl.conf

Below the sysctl.conf file

kern.sysv.shmmax=4194304
kern.sysv.shmmin=1
kern.sysv.shmmni=32
kern.sysv.shmseg=8
kern.sysv.shmall=1024
kern.sysv.semmsl=250
kern.sysv.semmns=32000
kern.sysv.semopm=100
kern.sysv.semmni=128

Do you know this issue ? is it a Bug or have you any idea on how to fix it?
Thanks for your help.

1) Moving to "Linux Guests" from "Mac OS X pre-releases". OSX 10.12.1 is not a pre-release version of OSX. It's the latest officially released version (as of this writing).

2) You have a problem with an application is your VM and you try to modify your host's kernel settings? Why did you created the sysctl.conf file in your OSX host? Did you followed a blog or something similar? It is very rare/extreme for an OSX computer to use this file.

3) Even it the case that you create the sysctl.conf file, those settings that you used do not even exist on your OSX version. Again, where did you get them from?

4) The only problem you seem to report is:

Mous wrote:I have an Ubuntu 15.04 VM and when trying to install Oracle 11g on it, I have "parameter.semmni failed Expected Value 128".

I don't see why this could be your host's issue. I didn't see a well detailed out case. Can you please try again?