Details
-
Type: Bug
-
Status: Verified
-
Priority: Major
-
Resolution: Fixed
-
Fix Version/s: Vz6.0-Update11-Hotfix8
-
Component/s: Containers::Kernel
-
Security Level: Public
Description
Description of problem:
We also need to change some fs.mqueue.* kernel parameters for POSIX Message Queues
fs.mqueue.msgsize_max=65536
fs.mqueue.msg_max=200
fs.mqueue.queues_max=512
But it's not possible to do inside the Container, even if it is set on the hardware nodes. Changes on Host do not affect guest OS.
>How reproducible:
>Steps to Reproduce:
We've set it on our OpenVZ Node but however inside of our container we've still got only default values
# sysctl -a |grep mqueue
fs.mqueue.queues_max = 512
fs.mqueue.msg_max = 200
fs.mqueue.msgsize_max = 65536
fs.mqueue.msg_default = 10
fs.mqueue.msgsize_default = 65365
Inside container:
# vzctl enter 666667
entered into CT 666667
# sysctl -a |grep mqueue
fs.mqueue.queues_max = 256
fs.mqueue.msg_max = 10
fs.mqueue.msgsize_max = 8192
fs.mqueue.msg_default = 10
fs.mqueue.msgsize_default = 8192
Actual results:
So for unpriviliged user/processes it is still not possible to open mqueues with messagesize greater and even other than 8192.... Same applies for the other fs.mqueue parameters as well...
>Expected results:
It should be possible to to open mqueues with messagesize greater and even other than 8192.Same applies for the other fs.mqueue parameters as well...
>Host OS:
Centos 6.7
# uname -r
2.6.32-042stab113.17
>Guest OS:
tested on
CentOS Linux release 7.1.1503 (Core)
and
CentOS release 6.7 (Final)
>Additional info (see https://openvz.org/Reporting_OpenVZ_problem):
https://forum.openvz.org/index.php?t=rview&goto=52410&th=12873
We also need to change some fs.mqueue.* kernel parameters for POSIX Message Queues
fs.mqueue.msgsize_max=65536
fs.mqueue.msg_max=200
fs.mqueue.queues_max=512
But it's not possible to do inside the Container, even if it is set on the hardware nodes. Changes on Host do not affect guest OS.
>How reproducible:
>Steps to Reproduce:
We've set it on our OpenVZ Node but however inside of our container we've still got only default values
# sysctl -a |grep mqueue
fs.mqueue.queues_max = 512
fs.mqueue.msg_max = 200
fs.mqueue.msgsize_max = 65536
fs.mqueue.msg_default = 10
fs.mqueue.msgsize_default = 65365
Inside container:
# vzctl enter 666667
entered into CT 666667
# sysctl -a |grep mqueue
fs.mqueue.queues_max = 256
fs.mqueue.msg_max = 10
fs.mqueue.msgsize_max = 8192
fs.mqueue.msg_default = 10
fs.mqueue.msgsize_default = 8192
Actual results:
So for unpriviliged user/processes it is still not possible to open mqueues with messagesize greater and even other than 8192.... Same applies for the other fs.mqueue parameters as well...
>Expected results:
It should be possible to to open mqueues with messagesize greater and even other than 8192.Same applies for the other fs.mqueue parameters as well...
>Host OS:
Centos 6.7
# uname -r
2.6.32-042stab113.17
>Guest OS:
tested on
CentOS Linux release 7.1.1503 (Core)
and
CentOS release 6.7 (Final)
>Additional info (see https://openvz.org/Reporting_OpenVZ_problem):
https://forum.openvz.org/index.php?t=rview&goto=52410&th=12873