2

I'm running a Wheezy box in KVM, by default it runs the kernel 3.2. After I upgrade to 3.14 from backports, I no longer can tune the IO scheduler.

Before:

# cat /sys/block/vda/queue/scheduler
noop deadline [cfq]

# echo noop > /sys/block/vda/queue/scheduler
# cat /sys/block/vda/queue/scheduler
[noop] deadline cfq

After:

# cat /sys/block/vda/queue/scheduler
none

# echo noop > /sys/block/vda/queue/scheduler
# cat /sys/block/vda/queue/scheduler
none

The host and VM configuration are untouched. What could be the problem?

bereal
  • 131
  • 1
  • 4

2 Answers2

1

The kernel you updated to likely does not have scheduler support you are looking for

e.g. you should be seeing something like this

egrep 'CONFIG_IOSCHED_.*=y' /boot/config-`uname -r`
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y

Where did you get that 3.14 kernel? If you were building it make sure you have those config options set for your build.

Hrvoje Špoljar
  • 5,245
  • 26
  • 42
0

This may be a feature rather than a bug. I am seeing the same on CentOS v7.1 https://access.redhat.com/solutions/1305843

Fred Flint
  • 678
  • 7
  • 6