Bug#410807: settings dom0_max_vcpus=1 is a workaround
I tried settings (dom0-cpus 1) in /etc/xen/xend-config.sxp and ended up
with 3 out of 4 cpu's in dom0... :\
xm vcpu-list output was something like this: (actual output is not in my
terminal scrollback buffer anymore...)
Name ID VCPUs CPU State Time(s) CPU Affinity
Domain-0 0 0 3 r-- 12.3 any cpu
Domain-0 0 1 2 r-- 45.6 any cpu
Domain-0 0 2 1 --p 78.9 any cpu
Domain-0 0 3 0 r-- 43.7 any cpu
So (dom0-cpus 1) seems to be broken. Instead of just using 1 cpu,
exactly one cpu was *not* used in dom0. Ehrmm.. ?
Also this did not solve the "kernel BUG at
drivers/xen/core/evtchn.c:481" issue, because dom0 froze again with the
same error.
Instead of using (dom0-cpus 1) in /etc/xen/xend-config.sxp I tried to
add dom0_max_vcpus=1 to grub:
title Xen 3.0.3-1-amd64 / Debian GNU/Linux, kernel 2.6.18-5-xen-amd64
root (hd0,0)
kernel /boot/xen-3.0.3-1-amd64.gz dom0_mem=256MB dom0_max_vcpus=1
com1=9600,8n1
module /boot/vmlinuz-2.6.18-5-xen-amd64 root=/dev/md0 ro console=tty0
console=ttyS0,9600n8
module /boot/initrd.img-2.6.18-5-xen-amd64
With succes:
mario.2 /etc/xen# xm vcpu-list
Name ID VCPUs CPU State Time(s) CPU
Affinity
Domain-0 0 0 0 r-- 46.5 any cpu
some-domU 5 0 3 -b- 3.3 any cpu
some-domU 5 1 1 -b- 2.2 any cpu
other-domU 6 0 2 -b- 3.4 any cpu
other-domU 6 1 3 -b- 1.7 any cpu
other-domU 6 2 0 -b- 1.1 any cpu
other-domU 6 3 2 -b- 1.3 any cpu
dom0 is only using one vcpu now.
Hans van Kranenburg
Reply to: