Bug#410807: workaround: linux-image-2.6.18-4-xen-amd64: Kernel BUG at drivers/xen/core/evtchn.c:481

Limiting the Dom0 number of cpus to 1 in /etc/xend-confix.xsp (dom0-cpus 1) cures the problem. Additional I've pinned Domain-0 vcpu0 to cpu0 (xm vcpu-pin 0 0 0) but this is not neccessary. # xm vcpu-list Name ID VCPUs CPU State Time(s) CPU Affinity Domain-00 0

Bug#410807: linux-image-2.6.18-4-xen-amd64: Kernel BUG at drivers/xen/core/evtchn.c:481

Package: linux-image-2.6.18-4-xen-amd64 Version: 2.6.18.dfsg.1-10snapshot.8256 Followup-For: Bug #410807 Bug 410807 is critical - renders XEN nearly unusable ! When starting up four xen paravirtualized domains quickly (no pause beetween the xm create) I sometimes get the attached kernel panic -