Bugzilla – Bug 1649
openvz kernel seems not to have ioprio configured
Last modified: 2010-11-05 11:13:31 EDT
Squeeze Openvz does not allow to start a container with a configured
IOPRIO variable ( http://wiki.openvz.org/Ioprio ).
Once the variable has commented out or removed the container can be started.
There is a possibility that vzctl has lost its capability to handle
ioprio correctly but I don't know of a way of verifying.
# vzctl set 102 --ioprio 2 --save
Saved parameters for CT 102
# grep IOPRIO /etc/vz/conf/102.conf
# vzctl start 102
Starting container ...
Container is mounted
Adding IP address(es): x.x.x.102
Setting CPU units: 1000
Warning: ioprio feature is not supported by kernel. skipped ioprio configure
Container start failed
Stopping container ...
Container was stopped
Container is unmounted
Debian bug tracker link http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596772
-- Package-specific info:
Linux version 2.6.32-5-openvz-686 (Debian 2.6.32-21)
(email@example.com) (gcc version 4.3.5 (Debian 4.3.5-2) ) #1 SMP Wed
Aug 25 16:19:28 UTC 2010
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-openvz-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Apparently this feature requires CONFIG_BLK_CGROUP, which is not available with stock 2.6.32 (only available from 2.6.33 according to http://cateee.net/lkddb/web-lkddb/BLK_CGROUP.html).
However, the OpenVZ patch contains this config, but it does not get enabled via the Debian build config.
It is likely to be an issue with Debian, and I will provide more information over there, after testing it.
I am closing this: after configuring CONFIG_BLK_CGROUP=y and CONFIG_CFQ_GROUP_IOSCHED=y this works with the Debian kernel.