vzctl doesnt limit cpulimit and cpus

Bug #254467 reported by Assid
8
Affects Status Importance Assigned to Milestone
vzctl (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: vzctl

vzctl lets you set resources on an VE.

However, I tried to set the cpulimit and cpus, but it just doesnt seem to work right.

I have this working flawlessly on a debian backport on a debian hostnode. The Ubuntu HN however, doesnt seem to work correctly. The cpulimit and cpus is just ignored.

Debian HN:
cpu MHz : 2394.092

VE on above HN
cpu MHz : 119.237

Ubuntu HN:
cpu MHz : 2394.110

VE on Ubuntu HN
cpu MHz : 2394.110

As you can see, I am unable to limit the cpu.

This is a big hazard, specially for anyone coming in thinking the cpu limit etc is working. A persons hardware node can spiral down if a VE spins out of control

Revision history for this message
Daniel Hahler (blueyed) wrote :

I think it's not a problem of vzctl, but probably some kernel bug.

However, I can confirm on a Hardy box, that "grep -i mhz /proc/cpuinfo" shows the same value on the hardware node and the virtual container (which is limited through CPUUNITS).

My understanding until now has been that the CPUUNITS would not change the reported CPU speed in the container(s).

Are you also using CPUUNITS to limit the cpu on both the Debian and Ubuntu HN?
What kernel versions are you using on the HNs ("uname -a").
The version of vzctl might also be interesting ("dpkg -s vzctl | grep Version:")

Changed in vzctl:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Daniel Hahler (blueyed) wrote :

http://<email address hidden>/msg01847.html states that "--cpu" and "--cpulimit" do not work with a 2.6.24 kernel.
So I guess your Debian HN is running on a more recent kernel?

Revision history for this message
Philip Muškovac (yofel) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for vzctl (Ubuntu) because there has been no activity for 60 days.]

Changed in vzctl (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.