Different Kernel Parameters in HN and VN

[shatter]

Hi *,

trying to install Oracle 11g on a Centos-5-64 container, I run into a peculiar problem: the kernel parameters "semmsl" and "semopm" are too small (100/32) - inside the container, although it's big enough (250/256) on the HN:

On VM:

[root@dhsrv1003vz ~]#  ipcs -l

------ Shared Memory Limits --------
max number of segments = 4096
max seg size (kbytes) = 524288
max total shared memory (kbytes) = 8388608
min seg size (bytes) = 1

------ Semaphore Limits --------
max number of arrays = 128
max semaphores per array = 100
max semaphores system wide = 32000
max ops per semop call = 32
semaphore max value = 32767

------ Messages: Limits --------
max queues system wide = 7992
max size of message (bytes) = 8192
default max size of queue (bytes) = 16384

On the HN:

nwivz:/# ipcs -l

------ Shared Memory Limits --------
max number of segments = 4096
max seg size (kbytes) = 524288
max total shared memory (kbytes) = 8388608
min seg size (bytes) = 1

------ Semaphore Limits --------
max number of arrays = 1024
max semaphores per array = 250
max semaphores system wide = 256000
max ops per semop call = 256
semaphore max value = 32767

------ Messages: Limits --------
max queues system wide = 7992
max size of message (bytes) = 8192
default max size of queue (bytes) = 16384

Is there a way to configure the VM so it uses the settings of the HN?

Thanx,

Joachim

 

[shatter]

forgotten:

nwivz:~# pveversion -v
pve-manager: 1.8-15 (pve-manager/1.8/5754)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.32: 1.8-32
pve-kernel-2.6.32-4-pve: 2.6.32-32
pve-kernel-2.6.24-8-pve: 2.6.24-16
qemu-server: 1.1-30
pve-firmware: 1.0-11
libpve-storage-perl: 1.0-16
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-11
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.14.0-2
ksm-control-daemon: 1.0-5

 

[dietmar]

I would use KVM instead.

 

[jfroebe]

Hey Joachim,

If your /etc/security/limits.conf *and* /etc/sysctl.conf in the host and vm are the same, then I would expect that to be an OpenVZ bug IMHO.

Going with a KVM vm for Oracle 11g would be the wrong decision unless it is used for as a development or small departmental db.

Jason