Re: [Xen-devel] xm pause causing lockup

[Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>]

Probably easiest way to trace this is with printk's in Xen. The guts of 
the work is done by domain_pause_by_systemcontroller() in xen/sched.h. 
This in turn calls domain_sleep() in common/schedule.c. A particularly 
interesting place to look will be teh synchronous spin loop at the end 
of domain_sleep -- if the paused domain isn't descheduled for some 
weird reason then the spin loop would never exit and domain0 would 
hang.
 -- Keir

On 14 Apr 2005, at 04:03, Kip Macy wrote:

> Dom0 is unpingable, all network connections timeout.
>
>                              -Kip
>
>
> > Does dom0 wedge completely (e.g., unpingable) or might it just be xend
> > that goes awol? The pause code isn't that complicated, and most of it
> > is used in various not uncommon situations, so I'll be surprised if
> > this is the hypervisor's fault.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel