OpenVZ Forum


Home » General » Support » tc not working in container (tc not working in container)
tc not working in container [message #39454] Mon, 26 April 2010 07:55 Go to next message
soldis is currently offline  soldis
Messages: 1
Registered: April 2010
Junior Member
Hello!

We have a problem when trying to make traffic shaping in containers. In HN everything works fine, but in containers all executions of tc returns the same:

[root@vpn01 tc]# /sbin/tc qdisc add dev eth0 root tbf rate 512Kbit latency 50ms burst 10000
RTNETLINK answers: Invalid argument


I mean all correct executions, so it is not the problem of this utility itself:

[root@vpn01 ~]# /sbin/tc qdisc add dev eth12 root tbf rate 512Kbit latency 50ms burst 10000
Cannot find device "eth12"


We've just installed new version of ALT Linux - platform 5 with kernel:

[root@vpn01 tc]# uname -a
Linux vpn01 2.6.27-ovz-smp-alt9 #1 SMP Tue Aug 18 09:29:34 UTC 2009 x86_64 GNU/Linux


We've also updated iproute2 and libnetlink to 2.6.33.

I've read on this forum that the problem may lie in the absence of /proc/psched inside containers - but I created file in local filesystem with the same values as /proc/pcshed in HN and recompiled tc such that it now takes values from this file - the same result. RTNETLINK does not want to communicate.

We have 64-bit HN and 64-bit containers.

Is it possible at all to have working shaping inside containers?
Re: tc not working in container [message #41045 is a reply to message #39454] Fri, 05 November 2010 20:57 Go to previous message
jwhite is currently offline  jwhite
Messages: 1
Registered: November 2010
Location: Montreal, Canada
Junior Member
I am also curious to know if anyone has got tc working inside a container. I can't seem to find any sources confirming that it does work.

-Jesse
Previous Topic: Host IPtables/Firewall
Next Topic: vzdump ERROR: got reserved VM ID '2'
Goto Forum:
  


Current Time: Wed Oct 02 07:21:16 GMT 2024

Total time taken to generate the page: 0.04641 seconds