2 ms·
xm sched-credit -d username -w 10 would have solved the CPU problem without doing anything more than slowing down the heavy user. Giving each guest a single C
by lsc 17y ago
xm sched-credit -d username -w 10
would have solved the CPU problem without doing anything more than slowing down the heavy user. Giving each guest a single CPU rather than all CPUs on the box also helps a lot. In fact, if your 'bad' user bought the same percentage of the box as everyone else, if you left the weights at their default levels, that user would get approximately their fair share of CPU.
Tip: if you don't dedicate a core to the Dom0, you will have problems if anyone else uses much cpu, disk, or network.
If you want to do the same for network, simply use tc: http://wiki.xen.prgmr.com/xenophilia/2008/06/traffic-shaping-with-tc-and-xe.html http://wiki.xen.prgmr.com/xenophilia/2008/06/traffic-shaping... - if your problem is disk, use ionice: http://wiki.xen.prgmr.com/xenophobia/2008/06/using-ionice1-to-mediate-disk.html http://wiki.xen.prgmr.com/xenophobia/2008/06/using-ionice1-t...
The whole point of providing Xen instances is that I don't want to muck around in your instance. It pisses you off, and it wastes my time. That's why I'm using xen, and not OpenVZ or some other glorified chroot. From the point of view of a provider, handling everything within the Dom0 not only makes customers more comfortable, it's also less work for you, the provider.