XEN auf RedHat Enterprise Linux 4 (RHEL4) AMD 64
XEN Manual - Using File-backed VBDs XEN Wiki
XEN and Shorewall
bugzilla for time went backwards bug
rtc läuft zu schnell auf AMD64
Xen Overview Installation Howto

XEN Installation Howto XEN China

XEN Virtual Manager

http://lists.xensource.com/archives/html/xen-devel/2004-04/msg00093.html You can select Atropos using sched=atropos as a boot param to Xen. The administrator tools (xc_dom_control.py and friends) don’t have support for actually configuring it yet (though there’s some library calls available in the Python Xc module if you want to write your own script) but I’ll be checking in basic support early next week.
See also docs/Sched-HOWTO.txt

http://lists.xensource.com/archives/html/xen-devel/2004-04/msg00091.html Xen schedules domains on the available CPUs pre-emptively, so CPU usage limiting should work just fine.
The default scheduler (BVT) is configured to provide an equal share of a CPU to each of the domains running on it. You can change the weights so that domains will get larger or smaller shares (there are some options in xc_dom_control.py).
A single domain shouldn’t be able to bog down the others on the system by its CPU usage in the default configuration. In fact, the plan is that disk and network usage will also be controllable so that you can give some guarantees on the slice of the machine a domain receives. [I think there are controls in place for network, mechanisms for disk are being worked on] I’ll be checking in a little documentation about the CPU schedulers next week. Eventually, we should have some kind of “friendly” user interface for controlling them. To solve your current problem, a little more information would be handy (e.g. what release you’re using, what scheduler you’re using, anything else that’s odd about the configuration, what configuration the domains have (what is it that is consuming 100% CPU in the domain, are the domains sharing any external resources that could cause performance problems), anything else you can think of).

http://article.gmane.org/gmane.comp.emulators.xen.user/10363 sEDF scheduler
Author: Stephan.Diestelhorst <at> {cl.cam.ac.uk, inf.tu-dresden.de}

This scheduler provides weighted CPU sharing in an intuitive way and uses realtime-algorithms to ensure time guarantees.

• add “sched=sedf” on Xen’s boot command-line
• create domains as usual
• use xm sched-sedf <dom-id> <period> <slice> <latency-hint> <extra> <weight>
  • period/slice are the normal EDF scheduling parameters in nanosecs
  • latency-hint is the scaled period in case the domain is doing heavy I/O (unused by the currently compiled version)
  • extra is a flag (0/1), which controls whether the domain can run in extra-time
  • weight is mutually exclusive with period/slice and specifies another way of setting a domains cpu slice

  normal EDF (20ms/5ms):
  xm sched-sedf <dom-id> 20000000 5000000 0 0 0

 best-effort domains (i.e. non-realtime):
  xm sched-sedf <dom-id> 20000000 0 0 1 0

 normal EDF (20ms/5ms) + share of extra-time:
  xm sched-sedf <dom-id> 20000000 5000000 0 1 0

 4 domains with weights 2:3:4:2
  xm sched-sedf <d1> 0 0 0 0 2
  xm sched-sedf <d2> 0 0 0 0 3
  xm sched-sedf <d3> 0 0 0 0 4
  xm sched-sedf <d4> 0 0 0 0 2

 1 fully-specified (10ms/3ms) domain, 3 other domains share
 available rest in 2:7:3 ratio:
  xm sched-sedf <d1> 10000000 3000000 0 0 0
  xm sched-sedf <d2> 0 0 0 0 2
  xm sched-sedf <d3> 0 0 0 0 7
  xm sched-sedf <d4> 0 0 0 0 3