Daniel Carosone <dan@geek.com.au> writes:

>  * Sometimes, all disk activity will stop, and something (usually the
>    cleaner) is stuck in biowait.  I suspect this to be a Xen issue.
>    Dom0 is linux with LVM2 volumes for the xbd backend, domU is
>    -current a day or two old.  It seems most easily (or even only?) 
>    triggered when dom0 is busy with CPU-heavy tasks.

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.

-- 
(let ((C call-with-current-continuation)) (apply (lambda (x y) (x y)) (map
((lambda (r) ((C C) (lambda (s) (r (lambda l (apply (s s) l))))))  (lambda
(f) (lambda (l) (if (null? l) C (lambda (k) (display (car l)) ((f (cdr l))
(C k)))))))    '((#\J #\d #\D #\v #\s) (#\e #\space #\a #\i #\newline)))))