Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I managed to create /cgroup/jail group, then I added (not through 'echo' command because permission denied error shows - maybe this is the problem?) chosen PID to tasks file and then '102' to cpu.shares (as 102 is 10% of cpu).
This process still uses more than 10% of cpu.
Anybody knows how to have it works fine?
I think that is a little deceptive.
You see, you are not LIMITING it to 10%, you are GUARENTEEING it 10%!
The system can give it MORE as long as there is more to give, but will always try to ensure that it has AT LEAST 10% available to it.
Well, I still think 102 in cpu.shares limit cpu power to 10% of physical cpu. But probably if other procesess don't use whole cpu power, even limited process can use more than 10%. Only when physical cpu usage reach 100%, cgroup limits included procesess.
I'm going to test this in virtual environment tomorrow and post the result.
My assumptions were right I guess. When physical CPU is 100% used, chosen procesess in cgroup are limited and can use only as much cpu power as I give them in cpu.shares.
But on the other hand I can say cgroups don't work too precisely (from what I saw in 'top').
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.