User`s guide

2. Shut down and reboot the host system.

• The root user in a container can affect the configuration of the host system by setting some /proc

entries. (Bug ID 17190287)

• Using yum to update packages inside the container that use init scripts can undo changes made by

the Oracle template.

• Migrating live containers (lxc-checkpoint) is not yet supported.

• Oracle Database is not yet supported for use with Linux Containers. The following information is

intended for those who want to experiment with such a configuration.

The following /proc parameter files may only be set on the host and not for individual containers:

• /proc/sys/fs/aio-max-nr

• /proc/sys/net/core/rmem_default

• /proc/sys/net/core/rmem_max

• /proc/sys/net/core/wmem_default

• /proc/sys/net/core/wmem_max

• /proc/sys/net/ipv4/ip_local_port_range

Setting the parameters in the host to the Oracle recommended values sets them for all containers

and allows the Oracle database to run in a container. For more information, see Configuring Kernel

Parameters. (Bug ID 17217854)

NUMA warning messages on a non-NUMA system

You can safely ignore the following warning messages in dmesg and /var/log messages if you see

them on a non-NUMA system:

kernel: NUMA: Warning: node ids are out of bound, from=-1 to=-1 distance=10

hcid[4293]: Register path:/org/bluez fallback:1

kernel: No NUMA configuration found

(Bug ID 13711370)

pcspkr driver error message

You can safely ignore the following error message:

Error: Driver 'pcspkr' is already registered, aborting...

The message arises from an alias conflict between snd-pcsp and pcspkr. To prevent the message from

being displayed, add the following line to /etc/modprobe.d/blacklist.conf:

blacklist snd-pcsp

(Bug ID 10355937)

sched_yield() settings for CFS

For the Unbreakable Enterprise Kernel, kernel.sched_compat_yield=1 is set by default. For the Red

Hat Compatible Kernel, kernel.sched_compat_yield=0 is used by default.