> I've just recently discovered something interesting with Xen3 that
> might be related: if the dom0 is running something that spins the CPU
> (like "perl -e '1 while 1'" or "yes > /dev/null") the NetBSD domU will
> not be run at all; it won't respond to the console nor to network
> traffic, and its timer event handler won't be called.  A Linux domU
> doesn't appear to have the same problem.

it's a characteristic of the default setting of sedf scheduler.
are you sure it doesn't happen for linux domU?

YAMAMOTO Takashi